dbcve.org
Use After FreeWeakness · CWE-416

CVE-2025-15062

HIGH · 7.8 CVSS v3.0 Published 2026-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Trimble SketchUp SKP File Parsing Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Trimble SketchUp. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of SKP files. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-27769.

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 · high confidence

Trimble SketchUp contains a use-after-free vulnerability in its SKP file parser. The flaw stems from the lack of validation that an object exists before performing operations on it, allowing an attacker to potentially reuse freed memory and execute arbitrary code in the context of the current process.

MitigationOrganizations should exercise caution when opening SKP files from untrusted sources. Apply vendor patches when available and consider deploying email/web filtering to block malicious SKP attachments.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify SketchUp installation
    Check if Trimble SketchUp is installed on the system. On Windows, look in C:\Program Files\SketchUp\ or use Programs and Features. On macOS, check /Applications for SketchUp.app. Alternatively, search for sketchup.exe (Windows) or SketchUp.app (macOS) using the system file explorer or command-line tools.
    Affected if SketchUp is present on the system
  2. Identify installed SketchUp version
    Retrieve the version number. On Windows: right-click SketchUp.exe, select Properties > Details > File Version, or launch SketchUp and go to Help > About SketchUp. On macOS: right-click SketchUp.app, select Get Info, or use Help > About SketchUp from within the application.
    Affected if Version is returned and can be compared to affected ranges
  3. Compare version to CVE scope
    Since specific version ranges are not provided in the CVE entry, compare your identified version to the affected versions listed in the official CVE-2025-15062 advisory from NIST or the vendor security bulletin. The vulnerability affects specific SketchUp versions in the SKP file parser.
    Affected if Installed version falls within the affected version range specified in the CVE
  4. Assess SKP file processing exposure
    The vulnerability is triggered when SketchUp parses a maliciously crafted SKP file. Check whether users in your environment routinely open SKP files from external or untrusted sources, as this is the attack vector.
    Affected if Users open SKP files, especially from external or untrusted sources

A user is affected if they have a SketchUp version within the affected range and open SKP files, since the use-after-free flaw in the SKP parser requires parsing a malicious file to trigger.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Organizations should exercise caution when opening SKP files from untrusted sources. Apply vendor patches when available and consider deploying email/web filtering to block malicious SKP attachments.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15062 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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