CVE-2026-47117

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-02. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
58%
KEV
Not listed

Published

June 2, 2026

Last Modified

August 28, 2026

Advisory Details (5)

Auto-updated Sep 11, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release.
generic

OpenMed < 1.5.2 Remote Code Execution via PII Model Loading | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openmed-remote-code-execution-via-pii-model-loading
github_release Patch Available

OpenMed v1.5.2

Patch available: maziyarpanahi/openmed v1.5.2

https://github.com/maziyarpanahi/openmed/releases/tag/v1.5.2
github_pr

Harden privacy-filter remote-code allowlist for 1.5.2

Fix merged in maziyarpanahi/openmed PR #59 on 2026-05-27 — awaiting tagged release

https://github.com/maziyarpanahi/openmed/pull/59
github_commit

commit 98724f65df98 (maziyarpanahi/openmed)

Fix landed in maziyarpanahi/openmed commit 98724f65df98 — awaiting tagged release

https://github.com/maziyarpanahi/openmed/commit/98724f65df98d7518b9006e6356740aa36c2f224
generic🟡 PoC Available

GitHub - SaiTeja-Erukude/CVE-2026-47117-openmed-rce: OpenMed < 1.5.2 unauthenticated RCE via PII privacy-filter model loading and trust_remote_code=True · GitHub

https://github.com/SaiTeja-Erukude/CVE-2026-47117-openmed-rce

Vendor Advisories for CVE-2026-47117(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
openmed0.1 ... 1.5.1 (37 versions)1.5.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 274 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 05:49 UTCEG score recompute
  3. 2026-09-13 16:47 UTCEPSS rescore
  4. 2026-09-12 15:01 UTCEPSS rescore
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 09:37 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 23:51 UTCEG score recompute
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 03:45 UTCEG score recompute
  22. 2026-08-23 13:42 UTCEG score recompute
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-22 00:16 UTCEG score recompute
  25. 2026-08-21 23:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 01:05 UTCEG score recompute
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-20 10:11 UTCEG score recompute
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-16 14:58 UTCEG score recompute
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 02:19 UTCEG score recompute
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 15:02 UTCEG score recompute
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-13 23:17 UTCEG score recompute
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-12 17:30 UTCEG score recompute
  15. 2026-08-12 13:51 UTCEPSS rescore
  16. 2026-08-11 13:54 UTCEG score recompute
  17. 2026-08-11 02:45 UTCEG score recompute
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-09 15:56 UTCEG score recompute
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-08 17:38 UTCEG score recompute
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-07 18:44 UTCEG score recompute
  24. 2026-08-06 15:13 UTCEG score recompute
  25. 2026-08-06 13:47 UTCEPSS rescore
  26. 2026-08-05 20:36 UTCEG score recompute
  27. 2026-08-05 19:17 UTCEPSS rescore
  28. 2026-08-04 19:55 UTCEG score recompute
  29. 2026-08-04 15:10 UTCEPSS rescore
  30. 2026-08-04 10:39 UTCEPSS rescore
  31. 2026-08-03 15:46 UTCEG score recompute
  32. 2026-08-03 10:36 UTCEPSS rescore
  33. 2026-08-02 04:22 UTCEG score recompute
  34. 2026-08-02 02:27 UTCEPSS rescore
  35. 2026-08-01 13:25 UTCEG score recompute
  36. 2026-08-01 04:16 UTCEPSS rescore
  37. 2026-07-31 05:38 UTCEG score recompute
  38. 2026-07-30 16:28 UTCEPSS rescore
  39. 2026-07-30 01:30 UTCEPSS rescore
  40. 2026-07-29 10:51 UTCEG score recompute
  41. 2026-07-28 15:37 UTCEPSS rescore
  42. 2026-07-26 22:55 UTCEG score recompute
  43. 2026-07-26 14:54 UTCEPSS rescore
  44. 2026-07-26 14:54 UTCEPSS rescore
  45. 2026-07-25 14:18 UTCEPSS rescore
  46. 2026-07-24 14:17 UTCEPSS rescore
  47. 2026-07-23 14:18 UTCEPSS rescore
  48. 2026-07-23 03:17 UTCEG score recompute
  49. 2026-07-22 14:08 UTCEPSS rescore
  50. 2026-07-21 15:24 UTCEPSS rescore
  51. 2026-07-20 17:08 UTCEPSS rescore
  52. 2026-07-19 14:31 UTCEPSS rescore
  53. 2026-07-19 02:29 UTCEPSS rescore
  54. 2026-07-18 10:04 UTCEPSS rescore
  55. 2026-07-16 17:03 UTCEPSS rescore
  56. 2026-07-15 16:57 UTCEPSS rescore
  57. 2026-07-15 02:00 UTCEPSS rescore
  58. 2026-07-13 22:30 UTCEPSS rescore
  59. 2026-07-13 06:13 UTCEPSS rescore
  60. 2026-07-12 05:46 UTCEPSS rescore
  61. 2026-07-11 08:27 UTCEPSS rescore
  62. 2026-07-09 19:10 UTCEPSS rescore
  63. 2026-07-08 15:16 UTCEPSS rescore
  64. 2026-07-07 13:46 UTCEPSS rescore
  65. 2026-07-06 16:27 UTCEPSS rescore
  66. 2026-07-06 02:23 UTCEPSS rescore
  67. 2026-07-05 02:30 UTCEPSS rescore
  68. 2026-07-04 06:31 UTCEPSS rescore
  69. 2026-07-01 15:07 UTCEPSS rescore
  70. 2026-06-30 23:22 UTCEPSS rescore
  71. 2026-06-30 08:19 UTCGHSA enrichment
  72. 2026-06-30 03:07 UTCGHSA enrichment
  73. 2026-06-29 23:12 UTCGHSA enrichment
  74. 2026-06-29 19:29 UTCGHSA enrichment
  75. 2026-06-29 14:56 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-47117?
CVE-2026-47117 is a critical vulnerability published on June 2, 2026. 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 modelname parameter, allowing a value such as attacker/foo-privacy-filter-bar to route through a path…
When was CVE-2026-47117 disclosed?
CVE-2026-47117 was first published in the National Vulnerability Database on June 2, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47117 actively exploited?
CVE-2026-47117 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 41.8% of all scored CVEs.
What is the CVSS score of CVE-2026-47117?
CVE-2026-47117 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-47117?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47117, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47117

Explore →

Is Your Infrastructure Affected by CVE-2026-47117?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs