Unauthenticated code execution via trusted model routing
Published Jun 2, 2026 · Updated Jun 2, 2026
Code injection in OpenMed before 1.5.2 allows remote attackers to execute arbitrary code through a crafted PII model name. The privacy-filter dispatcher uses substring matching to route the name into a Hugging Face loader with trust_remote_code enabled, importing custom code declared by auto_map. No authentication or user interaction is required, and the code runs with the privileges of the OpenMed service process.
Summary
What happened
Code injection in OpenMed before 1.5.2 allows remote attackers to execute arbitrary code through a crafted PII model name. The privacy-filter dispatcher uses substring matching to route the name into a Hugging Face loader with trust_remote_code enabled, importing custom code declared by auto_map. No authentication or user interaction is required, and the code runs with the privileges of the OpenMed service process.
The record
- CVE
- CVE-2026-47117
- Published
- Jun 2, 2026
- Updated
- Jun 2, 2026
- Vendor
- OpenMed
- Product
- OpenMed
- Classifications
- CWE-94, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 2, 2026CVE publishedPublication date reported by the CVE source.
- Jun 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.5.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo