Is pyassimp affected by CVE-2025-5167?

PyPI pyassimp is affected in <=5.4.3.

Is CVE-2025-5167 being exploited?

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

medium

CVE-2025-5167

Q: Is CVE-2025-5167 being exploited?

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

PyPI · pyassimp

Summary

A vulnerability was found in Open Asset Import Library Assimp 5.4.3. It has been declared as problematic. Affected by this vulnerability is the function LWOImporter::GetS0 in the library assimp/code/AssetLib/LWO/LWOLoader.h. The manipulation of the argument out leads to out-of-bounds read. The attac

Severity: medium
EPSS: 0.2% (p11)
Also known as: PYSEC-2025-174
Published: 2025-05-26

References

Related advisories

CVE-2025-2152 — critical · PyPI/pyassimp
CVE-2025-11277 — high · PyPI/pyassimp
CVE-2025-11275 — high · PyPI/pyassimp
CVE-2025-3158 — high · PyPI/pyassimp
CVE-2025-2757 — high · PyPI/pyassimp
CVE-2025-2756 — high · PyPI/pyassimp
CVE-2025-2755 — high · PyPI/pyassimp
CVE-2025-2754 — high · PyPI/pyassimp

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.