CVE-2026-10230
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability was identified in Assimp up to 6.0.4. This impacts the function Assimp::MDL::HalfLife::HL1MDLLoader::read_animations of the file HL1MDLLoader.cpp of the component Half-Life 1 MDL Loader. Such manipulation leads to heap-based buffer overflow. The attack must be carried out locally. The exploit is publicly available and might be used. The project tagged the reported issue as bug.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceHeap-based buffer overflow in Assimp::MDL::HalfLife::HL1MDLLoader::read_animations function in HL1MDLLoader.cpp when parsing malicious Half-Life 1 MDL files, potentially allowing code execution or denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Assimp library is presentCheck for Assimp installation: look for libassimp or assimp shared libraries in system paths (e.g., /usr/lib, /usr/local/lib) or search for 'assimp' in installed packages using package manager (dpkg -l, rpm -qa, or equivalent)Affected if Assimp library is installed on the system
-
Determine installed Assimp versionRun 'assimp version' if the command-line tool is available, or check library version via 'ldd' on linked executables, or inspect the shared library file version directlyAffected if Installed version is lower than the patched version (compare to any available security advisories)
-
Verify HL1MDLLoader module availabilityInspect Assimp's supported formats: run 'assimp info' on a test MDL file, or check Assimp's build configuration for 'IMPORT_MDL' support in cmake/build filesAffected if HL1MDLLoader is compiled into Assimp and available for use
-
Confirm MDL file processing in your applicationReview application code or logs to identify if any component loads or parses .mdl (Half-Life model) files using Assimp, check file input paths accepting MDL extensionsAffected if Application processes MDL files from any source, especially untrusted or user-supplied files
-
Check application context for untrusted inputExamine how MDL files reach the Assimp loader: via file upload, network import, or processing of user-supplied contentAffected if MDL files from untrusted sources are processed without prior validation
You are affected if Assimp with the HL1MDLLoader module is installed and your application processes untrusted or user-supplied Half-Life 1 MDL files using a version prior to the patched release.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Assimp to version 6.0.5 or later. Until patched, avoid processing untrusted MDL files and run applications using Assimp in sandboxed environments due to the local attack vector.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10230 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10230 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data