CVE-2026-47117: Security vulnerability
CVE-2026-47117 affects Hugging Face. The published description indicates a remote or untrusted-network exploitation path.
What happened
2 contains a remote code execution vulnerability in the PII privacy-filter model loading path. The privacy-filter dispatcher used broad substring matching on the user-supplied model_name parameter, allowing a value such as attacker/foo-privacy-filter-bar to route through a path that loads Hugging Face models with trust_remote_code=True. A security weakness in Hugging Face is being tracked as CVE-2026-47117.
CVE-2026-47117 affects Hugging Face. The reported consequence is code execution, meaning successful exploitation could make the affected application or process run attacker-controlled code. The published description indicates a remote or untrusted-network exploitation path.
The privacy-filter dispatcher used b. An unauthenticated attacker can supply a malicious model repos. The available description indicates that the vulnerable path can be reached remotely or from an untrusted network, so the exposure of Hugging Face becomes part of the attack condition.
Editorial note: this News Brief follows the available evidence and adds length only when additional facts or useful context are available. Where public reporting does not establish a specific victim sequence, CyberDeltaForce does not present one as fact.
What the reporting and advisory establish
2 contains a remote code execution vulnerability in the PII privacy-filter model loading path.
The privacy-filter dispatcher used broad substring matching on the user-supplied model_name parameter, allowing a value such as attacker/foo-privacy-filter-bar to route through a path that loads Hugging Face models with trust_remote_code=True.
An unauthenticated attacker can supply a malicious model repos
A security weakness in Hugging Face is being tracked as CVE-2026-47117. The available description indicates that the vulnerable path can be reached remotely or from an untrusted network, so the exposure of Hugging Face becomes part of the attack condition. The reported consequence is code execution, meaning successful exploitation could make the affected application or process run attacker-controlled code. The privacy-filter dispatcher used broad substring matching on the user-supplied model_name parameter, allowing a value such as attacker/foo-privacy-filter-bar to route through a path that loads Hugging Face models with trust_remote_code=True. An unauthenticated attacker can supply a malicious model repos. The issue currently carries a CRITICAL 9.8 severity signal in the available reporting.
What this means for your environment
Move from the published facts to the technical path, exposure conditions and defensive decisions that matter in a real environment.
Attack & Exploitation Path
The sequence below shows how the vulnerability can be reached and what successful exploitation can produce. Each stage is labeled by evidence status.
an affected Hugging Face instance is reachable from a network or remote position available to the attacker.
attacker-controlled network input reaches the vulnerable code path on the affected service.
the the reported vulnerability condition is triggered inside Hugging Face, creating the security boundary failure described by the advisory.
successful exploitation can result in attacker-controlled code execution in the affected application or process.
the practical reach of successful code execution depends on the privileges and resources available to the affected process.
Why this matters to you
CVE-2026-47117 matters because the practical risk is not the score alone — it is whether Hugging Face exists in your environment and whether the reported trigger or exposure path can reach it. The current severity is CRITICAL 9.8. No exploitation flag is currently present in the CDF data, but that does not remove the need to validate affected systems.
Does this deserve attention in my environment?
Check the conditions below against your use of Hugging Face.
Select the conditions that are true in your environment. Leaving a condition unselected does not mean you are safe — it only means you have not marked it as applicable.
- Search endpoint, software and asset inventory for Hugging Face.
- Confirm the vendor-recommended fixed version or mitigation and verify deployment, not just assignment, across affected assets.
- Review relevant endpoint, application, network or identity telemetry for activity associated with exploitation of the affected component.
- Track vendor and government guidance for any change in exploitation status while remediation is underway.
What remains unconfirmed
- Available reporting does not currently indicate exploitation, but that can change as vendor, government or threat-intelligence reporting develops.
Sources & References
Original reporting and technical references are kept here for readers who want to verify the facts. Publisher names stay out of the reading flow above.