CVE Intelligence
Skip to main content
mediumRemote Code Execpublic exploit

CVE-2026-19969

CVE-2026-19969 — Open Asset Import Library Assimp 3DGS MDL7 Model Output Mesh Generator MDLLoader.cpp GenerateOutputMeshes_3DGS_MDL7 buffer overflow

A security vulnerability has been detected in Open Asset Import Library Assimp 17c12da. The impacted element is the function Assimp::MDLImporter::GenerateOutputMeshes_3DGS_MDL7 of the file code/AssetLib/MDL/MDLLoader.cpp of the component 3DGS MDL7 Model Output Mesh Generator. The manipulation leads to buffer overflow. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Published Updated Sources: NVD, Open Asset Import Library (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

0%

ahead of 0% of scored CVEs

Affects

Open Asset Import Library

Assimp

CVSS base

5.4

medium · 6 sources

Remediation

The vendor's own words where we have them.

Upgrade Assimp to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
Open Asset Import LibraryAssimp17c12daVulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

Low

Confidentiality

None

Integrity

Low

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

Required

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
5.4CVSS 3.1medium2.82.5NVD
6.4CVSS 2.0medium104.9vuldb.com (CNA)
5.3CVSS 4.0medium——Open Asset Import Library (CNA)
5.4CVSS 3.1medium——Open Asset Import Library (CNA)
5.4CVSS 3.0medium——Open Asset Import Library (CNA)
6.4CVSS 2.0medium——Open Asset Import Library (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

  • Modify Memory
  • Execute Unauthorized Code or Commands
  • DoS: Crash, Exit, or Restart
  • DoS: Resource Consumption (CPU)

Mitigation: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.

CWE-119 · Improper Restriction of Operations within the Bounds of a Memory Buffer

  • Execute Unauthorized Code or Commands
  • Modify Memory
  • Read Memory
  • DoS: Crash, Exit, or Restart

Mitigation: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.

Weakness & attack patterns

  • CWE-120
  • CWE-119

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-100 · Overflow BuffersCAPEC-8 · Buffer Overflow in an API CallCAPEC-92 · Forced Integer OverflowCAPEC-67 · String Format Overflow in syslog()CAPEC-24 · Filter Failure through Buffer OverflowCAPEC-10 · Buffer Overflow via Environment VariablesCAPEC-47 · Buffer Overflow via Parameter ExpansionCAPEC-44 · Overflow Binary Resource FileCAPEC-42 · MIME ConversionCAPEC-14 · Client-side Injection-induced Buffer OverflowCAPEC-9 · Buffer Overflow in Local Command-Line UtilitiesCAPEC-45 · Buffer Overflow via Symbolic Links

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

2

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /AssetLib/MDL/MDLLoader.cpp.
  • Prioritize edge telemetry for network-reachable Assimp.
  • Monitor for scanner or exploit-pattern traffic after 2 public PoC repositories were reported.
web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026

  2. Added · CVSS 3.1 5.4 (AV:N)

    Aug 17, 2026 · NVD

  3. Initial · CVE published

    Aug 17, 2026 · NVD

  4. CVE published by mitre

    Aug 17, 2026 · SOCRadar CTI

  5. Reported · Advisory disclosed

    Aug 16, 2026 · Open Asset Import Library

  6. Reported · VulDB entry created

    Aug 16, 2026 · Open Asset Import Library

  7. Reported · VulDB entry last update

    Aug 16, 2026 · Open Asset Import Library

References

6 on the record

Coverage

1 story from the feeds we poll

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-19969 is Open Asset Import Library Assimp 3DGS MDL7 Model Output Mesh Generator MDLLoader.cpp GenerateOutputMeshes_3DGS_MDL7 buffer overflow, a medium vulnerability affecting Assimp from Open Asset Import Library. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-19969. Public exploit evidence is: 2 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 5.4 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.