CVE-2026-47117
A public proof of concept exists; no exploitation attested.
- Published2026-06-02
- Fixed in1.5.2
- WeaknessCWE-94
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
OpenMed before 1.5.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 repository containing custom Transformers code via auto_map in config.json or tokenizer_config.json, which is imported and executed with the privileges of the OpenMed service process.
Timeline
dates in UTC- 2026-06-0216:16CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-47117?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-47117?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
OSV| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.5 | < 1.5.2 | 1.5.2 | OSV |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update openmed to 1.5.2
Detection
read 2026-10-23 19:25 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 1 repository, unverifiedSaiTeja-Erukude/CVE-2026-47117-openmed-rce PoC-in-GitHub
Sources
- NVDCVE recordread 2026-10-23
- CISA-ADPSSVC decisionnone2026-06-02
- OpenCVESSVC decisionnone—
- CNACVSS 4.09.3read 2026-10-23
- CNACVSS 3.19.8read 2026-10-23
- CNAweakness (CWE)CWE-94read 2026-10-23
- FIRST EPSSEPSS score1.3 %2026-10-22
- PoC-in-GitHubproof of concept1read 2026-10-23
- OSVaffected packages—
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CVSS 4.0 vector
- CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- Published
- 2026-06-02
- Last Modified
- 2026-10-08
- NVD status
- Deferred
Frequently asked questions
What is CVE-2026-47117?
Is CVE-2026-47117 actively exploited?
What is the CVSS score for CVE-2026-47117?
Running openmed? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.