openmed (pypi) has 1 known vulnerability, the worst rated CRITICAL. Upgrade to 1.5.2 or later to clear it. No malicious-package signal is recorded.
136 direct dependencies
59 carry known advisories, worst CRITICAL
0 packages depend on it
an advisory here reaches each of them
No published models are known to use this package.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days, 61st percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-m3v4-v5gx-7wf5, the advisory selected below
OpenMed before 1.5.2 contains a remote code execution vulnerability in the PII privacy-filter model loading path.
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for openmed (pypi), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 1 known vulnerability for openmed (pypi), the worst rated CRITICAL. They are GHSA-m3v4-v5gx-7wf5.
1.5.2 or later clears every advisory recorded for openmed (pypi). Check the release you pick before installing it.
Search openmed in CyberXYZ Check at https://cyberxyz.io/check?q=openmed. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 13:02 UTC. The most recent advisory here was published 2026-06-02. Updated continuously from NVD, GHSA, OSV and CNA feeds.