LiveActive security incident?Get immediate response
CVE Record

CVE-2026-10200: Assimp 4x4 Matrix glTFCommon.h CopyValue heap-based overflow

A vulnerability was found in Assimp up to 6.0.4. This affects the function glTFCommon::CopyValue in the library glTFCommon.h of the component 4x4 Matrix Parser. Performing a manipulation results in heap-based buffer overflow. The attack must be initiated from a local position. The exploit has been made public and could be used. The project tagged the reported issue as bug.

MediumCVSS 5.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Assimp versions 6.0.0 through 6.0.4 can overflow heap memory while parsing certain glTF 4x4 matrix data. The issue is local and requires privileges, so it is most urgent where users or pipelines process untrusted 3D assets.

Executive priority

Treat as a moderate-priority dependency exposure. Prioritize teams that process untrusted 3D assets or allow authenticated users to submit models, because public exploit material increases follow-on risk despite the local attack vector.

Technical view

The flaw affects glTFCommon::CopyValue in glTFCommon.h, within Assimp's 4x4 Matrix Parser. Manipulated input can cause a heap-based buffer overflow, mapped to CWE-119 and CWE-122. CVSS is 5.3 with AV:L, PR:L, UI:N, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely in applications, build pipelines, scanners, or content tools using Assimp 6.0.0-6.0.4 to process glTF assets. Public internet exposure depends on whether the application lets users upload or submit 3D model files.

Exploitation context

The bundle says exploit material is public and could be used, but KEV is false and no source states active exploitation. The attack is local, low complexity, and requires low privileges without user interaction.

Researcher notes

Evidence is limited to VulDB, CVE metadata, and the Assimp issue references in the bundle. No confirmed fixed release, vendor advisory text, or active exploitation evidence is provided. Avoid assuming broader remote impact unless an application exposes Assimp parsing to uploaded files.

Mitigation direction

  • Inventory direct and transitive Assimp usage, especially versions 6.0.0 through 6.0.4.
  • Restrict processing of untrusted glTF assets until vendor guidance is available.
  • Run asset parsing with least privilege and crash isolation where feasible.
  • Monitor the Assimp issue and VulDB entry for confirmed fixed versions.
  • Update Assimp when the project publishes a supported remediation.

Validation and detection

  • Confirm deployed Assimp versions in products, tools, and CI pipelines.
  • Identify workflows that parse glTF files or imported 3D assets.
  • Check whether local or authenticated users can submit assets for parsing.
  • Review crash telemetry for heap overflow failures in Assimp import paths.
  • Track the GitHub issue for vendor confirmation and remediation status.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-119: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-122: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-10200 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

4CVSS vectors
6Timeline events
0ADP providers
8Source links

CVSS vector scores

4 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R1.83.4VulDB
5.3CVSS 3.0MediumCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R1.83.4VulDB
4.8CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P——VulDB
4.3CVSS 2.0MediumAV:L/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR3.16.4VulDB

Vulnerability scoring details

Base CVSS 4.0 score

4.8Medium
CVSS 4.0 vector shape for CVE-2026-10200Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineVulDB

    Advisory disclosed

  2. Source timelineVulDB

    VulDB entry created

  3. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timelineVulDB

    VulDB entry last update

  5. CVE publishedCVE Program

    The CVE record was published.

  6. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aAssimp6.0.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4Listed
Weakness

CWE details

CWE-119CWE-122

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-119 · source CWE mapping

Improper Restriction of Operations within the Bounds of a Memory Buffer

Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs
CWE-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs