Home/CVE/Claude Code is an agentic coding tool. From 0.2.54 until 2.1.163, because the hostname huggingface.co was pre-approved
CVE
↯ PDF report

CVE-2026-543161

Claude Code is an agentic coding tool. From 0.2.54 until 2.1.163, because the hostname huggingface.co was pre-approved

Claude Code is an agentic coding tool. From 0.2.54 until 2.1.163, because the hostname huggingface.co was pre-approved as a bare hostname for the WebFetch tool, any path on that domain-including attacker-controlled model repositories-was auto-approved without a permission prompt or being subject to --allowedTools restrictions. An attacker able to inject untrusted content into a Claude Code context could direct it to issue WebFetch requests against attacker-controlled repository files (e.g. /resolve/main/config.json), which HuggingFace counts as downloads server-side, creating a covert out-of-band channel for encoding and exfiltrating data Claude can access such as files, environment variables, or command output.

Reliably exploiting this required the ability to add untrusted content into a Claude Code context window. This vulnerability is fixed in 2.1.163.

Schedule remediation
  • Public exploit or PoC is available
  • ⚠ NVD has not scored this CVE yet - manual triage required (common for recent CVEs)
No Sigma yet — build one → YARA rules0
Look this up elsewhere - one-click external pivots
NVDCVE.orgCISAExploit-DBGitHub PoCVulnCheck KEVGreyNoise
▸ How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-54316, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
⚠

Exploitation evidence

1 of 7 sources
Corroboration score 8/100 · emerging. This counts how many independent sources have exploitation evidence, and separates two different things: confirmed in-the-wild use (CISA KEV, Microsoft MSRC, ransomware activity) from exploit / PoC availability (Metasploit, ExploitDB, Nuclei, public PoCs). A template or PoC existing means an attack is possible and easy - it is not, on its own, proof the CVE is being exploited in the wild.
Exploit / PoC available
public PoC
⚠

Public Exploits & PoCs

1
These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted. Signed-in users mark whether it works, rate 1-10, and can report malware with a required reason that becomes a public comment.
poc InertFluid/cve-2026-54316-lab (nomi-sec)↗ date unknown
⋮
Vote & rate
Report or claim
⚠ Report this PoC

Becomes a public comment attributed as First L. (never full last name). Don't include private info. Rate-limited: 5/hour.

Works? no reports yet
Rating -
◆

ATT&CK techniques

20

Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.

T1007 · System Service Discovery T1016 · System Network Configuration Discovery T1018 · Remote System Discovery T1033 · System Owner/User Discovery T1036.005 · Match Legitimate Resource Name or Location T1046 · Network Service Discovery T1049 · System Network Connections Discovery T1057 · Process Discovery T1069 · Permission Groups Discovery T1082 · System Information Discovery T1083 · File and Directory Discovery T1087 · Account Discovery T1111 · Multi-Factor Authentication Interception T1120 · Peripheral Device Discovery T1124 · System Time Discovery T1134.001 · Token Impersonation/Theft T1135 · Network Share Discovery T1217 · Browser Information Discovery T1550.004 · Web Session Cookie T1574.006 · Dynamic Linker Hijacking
▤ Build a SIEM detection for these techniques
▤

CAPEC attack patterns

12

Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.

CAPEC-CAPEC-116 · Excavation CAPEC-CAPEC-120 · Double Encoding CAPEC-CAPEC-13 · Subverting Environment Variable Values CAPEC-CAPEC-169 · Footprinting CAPEC-CAPEC-22 · Exploiting Trust in Client CAPEC-CAPEC-224 · Fingerprinting CAPEC-CAPEC-285 · ICMP Echo Request Ping CAPEC-CAPEC-287 · TCP SYN Scan CAPEC-CAPEC-290 · Enumerate Mail Exchange (MX) Records CAPEC-CAPEC-291 · DNS Zone Transfers CAPEC-CAPEC-292 · Host Discovery CAPEC-CAPEC-293 · Traceroute Route Enumeration
⬡

Weakness Classification

CWE-183Permissive List of Allowed Inputs
CWE-200Exposure of Sensitive Information to an Unauthorized Actor
CWE-515Covert Storage Channel
▤

Affected Packages

1
Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
npm @anthropic-ai/claude-code MODERATE fixed in 2.1.163
▤

Related CVEs

8
CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row.
CVE-2020-1694 A flaw was found in all versions of Keycloak before 10.0.0, where the NodeJS ada... same CWE-183 MEDIUM CVE-2020-25696 A flaw was found in the psql interactive terminal of PostgreSQL in versions befo... same CWE-183 HIGH CVE-2021-34787 A vulnerability in the identity-based firewall (IDFW) rule processing feature of... same CWE-183 MEDIUM CVE-2021-40128 A vulnerability in the account activation feature of Cisco Webex Meetings could ... same CWE-183 MEDIUM CVE-1999-0059 IRIX fam service allows an attacker to obtain a list of all files on the server. same CWE-200 HIGH CVE-1999-0524 ICMP information such as (1) netmask and (2) timestamp is allowed from arbitrary... same CWE-200 MEDIUM CVE-1999-1136 Vulnerability in Predictive on HP-UX 11.0 and earlier, and MPE/iX 5.5 and earlie... same CWE-200 CVE-1999-0453 An attacker can identify a CISCO device by sending a SYN packet to port 1999, wh... same CWE-200
🔗

References & Sources

1
Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.
https://github.com/anthropics/claude-code/security/advisories/GHSA-fg94-h982-f3mm
◈SOC and Response
◆Detection Engineering
◎Threat Hunting
▲Red Team and Pentest
■Compliance and GRC
◯About
threatengine.sh