Is pyassimp affected by CVE-2025-3158?

PyPI pyassimp is affected in <=5.4.3.

Is CVE-2025-3158 being exploited?

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

high

CVE-2025-3158

Q: Is CVE-2025-3158 being exploited?

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

PyPI · pyassimp

Summary

A vulnerability, which was classified as critical, has been found in Open Asset Import Library Assimp 5.4.3. Affected by this issue is the function Assimp::LWO::AnimResolver::UpdateAnimRangeSetup of the file code/AssetLib/LWO/LWOAnimation.cpp of the component LWO File Handler. The manipulation leads

Severity: high
EPSS: 0.3% (p17)
Also known as: PYSEC-2025-169
Published: 2025-04-03

References

Related advisories

CVE-2025-2152 — critical · PyPI/pyassimp
CVE-2025-11277 — high · PyPI/pyassimp
CVE-2025-11275 — 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
CVE-2025-2753 — 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.