CVE-2025-57108
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 · uneditedKitware VTK (Visualization Toolkit) through 9.5.0 contains a heap use-after-free vulnerability in vtkGLTFDocumentLoader. The vulnerability manifests during mesh object copy operations where vector members are accessed after the underlying memory has been freed, specifically when handling GLTF files with corrupted or invalid mesh reference structures.
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 use-after-free vulnerability in VTK's vtkGLTFDocumentLoader component. The flaw occurs during mesh object copy operations where vector members are accessed after underlying memory has been freed, triggered by loading GLTF files with corrupted or invalid mesh reference structures. This memory safety issue in the file parsing code could allow arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 9.5.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 installed VTK versionRun 'vtkVersion' from Python (import vtk; print(vtk.vtkVersion.GetVTKVersion())) or check package manager (pip show vtk, conda list vtk, or rpm -q vtk). Compare the version number to the affected range <= 9.5.0Affected if Installed version is 9.5.0 or lower (any version up to and including 9.5.0)
-
Verify vtkGLTFDocumentLoader is availableCheck if the GLTF loader module exists in the VTK installation: import vtk; print(hasattr(vtk, 'vtkGLTFDocumentLoader')) or list files containing 'gltf' in the VTK lib directoryAffected if The vtkGLTFDocumentLoader component is present in the VTK build
-
Confirm GLTF file processing is occurringReview application logs, code, or runtime environment for instances of vtkGLTFDocumentLoader being instantiated (look for 'vtkGLTFDocumentLoader' in source code or dynamic library loading). Check if the application loads or parses .gltf or .glb filesAffected if The application uses vtkGLTFDocumentLoader to load GLTF/GLB files
-
Assess source of GLTF filesAudit the application's file input sources: determine if GLTF files originate from untrusted or user-supplied sources (web uploads, file uploads, network endpoints, or any external input)Affected if GLTF files from untrusted sources are being processed by the vulnerable component
A user is affected if they have VTK version 9.5.0 or lower AND the vtkGLTFDocumentLoader is processing GLTF files, especially from untrusted sources.
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 VTK to a version beyond 9.5.0 when patch is released; until then, avoid processing untrusted GLTF files with VTK to prevent exploitation.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-57108 — 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-2025-57108 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