Is aim affected by CVE-2025-5321?

PyPI aim is affected in <=3.29.1.

Is CVE-2025-5321 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.5%.

low

CVE-2025-5321

Q: Is CVE-2025-5321 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.5%.

PyPI · aim

Summary

Aim Vulnerable to Sandbox Escape Leading to Remote Code Execution

Severity: low
EPSS: 0.5% (p38)
Also known as: GHSA-gp5h-f9c5-8355
Published: 2025-05-29

References

https://nvd.nist.gov/vuln/detail/CVE-2025-5321
https://gist.github.com/superboy-zjc/1fc4747a0ac77a1edc8c32e1d4edc54c
https://github.com/aimhubio/aim

Related advisories

CVE-2024-8769 — critical · PyPI/aim
CVE-2024-6829 — critical · PyPI/aim
CVE-2025-0189 — high · PyPI/aim
CVE-2025-0190 — high · PyPI/aim
CVE-2024-8061 — high · PyPI/aim
CVE-2024-7760 — high · PyPI/aim
CVE-2024-6851 — high · PyPI/aim
CVE-2024-12778 — high · PyPI/aim

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.