CVE-2026-47117: OpenMed vulnerable to remote code injection through privacy-filter model loading path
(updated )
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.
References
- github.com/advisories/GHSA-m3v4-v5gx-7wf5
- github.com/maziyarpanahi/openmed/commit/98724f65df98d7518b9006e6356740aa36c2f224
- github.com/maziyarpanahi/openmed/pull/59
- github.com/maziyarpanahi/openmed/releases/tag/v1.5.2
- nvd.nist.gov/vuln/detail/CVE-2026-47117
- www.vulncheck.com/advisories/openmed-remote-code-execution-via-pii-model-loading
Code Behaviors & Features
Detect and mitigate CVE-2026-47117 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →