Skip to main content
← Vulnerabilities

Pixar Animation Studio OpenUSD Crate File Parsing Double Free Remote Code Execution Vulnerability

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

7.8HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Processing USDC or USDZ files with the OpenUSD crate file parser

18Pcve.now Index 18 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity7.8/10CVSS 7.8
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 28 if CISA's SSVC rates it automatable

CVE-2026-92211 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 OpenUSD; no fixed version is listed yet.

Published
Last modified
Published
Not listed in CISA KEV
18/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

Pixar's OpenUSD library, which processes Universal Scene Description files such as USDC and USDZ, is affected. An attacker who gets a crafted file processed by the library could trigger a double free and run arbitrary code within the affected application's process.

Read the original description

Pixar Animation Studio OpenUSD Crate File Parsing Double Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Pixar Animation Studio OpenUSD. Interaction with this library is required to exploit this vulnerability but attack vectors may vary depending on the implementation. The specific flaw exists within the parsing of USDC and USDZ files. The issue results from the lack of validating the existence of an object prior to performing further free operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-30428.

What to do

  • Check whether your setup matches what the bug needs.

    Processing USDC or USDZ files with the OpenUSD crate file parser
  • Workaround: The facts list no workaround. The only stated trigger is processing USDC or USDZ files with the crate parser, so limiting that processing is the one lever the facts point to.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Pixar Animation Studio OpenUSD

    v26.03

Evidence 2

  1. Advisory
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-92211

Is CVE-2026-92211 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: cve.now feed data

What does this mean?

The flaw is a double free in the OpenUSD crate file parser, triggered when USDC or USDZ files are parsed. According to the advisory, it could allow arbitrary code to run in the context of the current process.Source: zerodayinitiative.com

Which versions are affected by CVE-2026-92211?

OpenUSD: version v26.03.Source: cve.now feed data

Am I affected, and how do I check?

The facts list no version ranges, so the affected versions are not stated. The affected setup is processing USDC or USDZ files with the OpenUSD crate file parser, so a reader can check whether their OpenUSD build handles those file types.Source: zerodayinitiative.com

How do I fix CVE-2026-92211?

The facts name no fixed version or update target. Check the vendor's advisory for a patched release before deciding what to install.Source: zerodayinitiative.com

What if there's no patch?

The facts list no workaround. The only stated trigger is processing USDC or USDZ files with the crate parser, so limiting that processing is the one lever the facts point to.Source: zerodayinitiative.com

Why do the sources disagree?

The description calls this a remote vulnerability, but the CVSS vector records the attack vector as local (AV:L). The sources conflict on how the attack is delivered, and the facts do not resolve which is correct.Source: zerodayinitiative.com