# CVE-2025-3160: Open Asset Import Library Assimp File SceneCombiner.cpp AddNodeHashes out-of-bounds > A local attacker can trigger an out-of-bounds read in Assimp's SceneCombiner, potentially causing crashes or leaking memory contents. - **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 3 Apr 2025 - **Updated:** 3 Apr 2025 - **Also known as:** DEBIAN-CVE-2025-3160, GHSA-5jfr-9rr4-m9qm, PYSEC-2025-264, UBUNTU-CVE-2025-3160 ## What is CVE-2025-3160? CVE-2025-3160 is a medium-severity memory corruption vulnerability in Open Asset Import Library Assimp, published on 3 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A vulnerability has been found in Open Asset Import Library Assimp 5.4.3 and classified as problematic. This vulnerability affects the function Assimp::SceneCombiner::AddNodeHashes of the file code/Common/SceneCombiner.cpp of the component File Handler. The manipulation leads to out-of-bounds read. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The patch is identified as a0993658f40d8e13ff5823990c30b43c82a5daf0. It is recommended to apply a patch to fix this issue. Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2025-3160? 1 open source package ship an affected version, including pyassimp. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `pyassimp` | PyPI | All versions to 5.4.3 | None | Products: Assimp Assimp. ## How do I fix CVE-2025-3160? Apply the vendor's patch. ## Is CVE-2025-3160 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3160 exists. ## Other vulnerabilities in Open Asset Import Library Assimp - [CVE-2022-45748](https://insights.sbomify.com/CVE-2022-45748/): Use after free in n/a (high 8.8) - [CVE-2024-48423](https://insights.sbomify.com/CVE-2024-48423/): Use after free in n/a (high 8.4) - [CVE-2024-45679](https://insights.sbomify.com/CVE-2024-45679/): Memory corruption in Assimp (high 8.4) - [CVE-2024-40724](https://insights.sbomify.com/CVE-2024-40724/): Memory corruption in Assimp (high 8.4) - [CVE-2022-38528](https://insights.sbomify.com/CVE-2022-38528/): Null dereference in n/a (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-3160 and fix it if it is affected. What it is: CVE-2025-3160 is a medium-severity memory corruption vulnerability in Open Asset Import Library Assimp, published on 3 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3160 exists. Affected packages and fixed versions: - pyassimp (PyPI): affected all versions up to 5.4.3; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-3160/ (Markdown: https://insights.sbomify.com/CVE-2025-3160/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3160 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3160 - OSV: https://osv.dev/vulnerability/CVE-2025-3160 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-3160/ Summaries are generated and may contain mistakes; the official description above is the record.