CVE-2022-42268
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 · uneditedOmniverse Kit contains a vulnerability in the reference applications Create, Audio2Face, Isaac Sim, View, Code, and Machinima. These applications allow executable Python code to be embedded in Universal Scene Description (USD) files to customize all aspects of a scene. If a user opens a USD file that contains embedded Python code in one of these applications, the embedded Python code automatically runs with the privileges of the user who opened the file. As a result, an unprivileged remote attacker could craft a USD file containing malicious Python code and persuade a local user to open the file, which may lead to information disclosure, data tampering, and denial of service.
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 confidenceOmniverse Kit applications (Create, Audio2Face, Isaac Sim, View, Code, Machinima) automatically execute Python code embedded in USD files upon file open, running with the privileges of the opening user. This allows untrusted USD files to inject and execute arbitrary Python code, enabling information disclosure, data tampering, or denial of service.
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< 2022.2.0< 2022.2< 2022.3.0< 2022.3< 2022.3< 2022.2.1CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Omniverse applicationsCheck your system for any of the following Omniverse Kit applications: Create, Audio2Face, Isaac Sim, View, Code, or Machinima. Look in standard installation directories or your system's application list.Affected if Any of these applications are installed on the system
-
Determine installed version of each Omniverse appOpen the application and navigate to Help > About or check the application launcher for the version number. Compare the installed version against the affected ranges: Isaac Sim < 2022.2.0, Audio2Face < 2022.2, Code < 2022.3.0, Create < 2022.3, Machinima < 2022.3, View < 2022.2.1Affected if The installed version falls within any of these affected version ranges
-
Locate USD file to inspectIdentify the specific USD file you intend to open or have recently opened with the Omniverse application. This file may come from an external source or untrusted origin.Affected if You are opening or have opened USD files from untrusted or unknown sources
-
Verify if embedded Python code exists in USD fileOpen the USD file in a text editor or use a USD tool to examine the file contents. Look for Python script tags or embedded code blocks within the USD structure that would execute automatically upon file load.Affected if The USD file contains embedded Python code that would execute automatically on file open
-
Check application settings for Python executionIn the Omniverse application, go to Settings or Preferences and look for options related to Python script execution, automatic script loading, or USD Python runtime settings. Check if automatic execution is enabled without user prompts.Affected if Automatic Python execution in USD files is enabled without user authorization or prompts
You are affected if you have any of the listed Omniverse applications installed with a version below the specified thresholds and you open USD files (especially from untrusted sources) with automatic Python execution enabled.
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.
dbcve · scoped2022.22022.2.02022.2.1
Disable automatic Python execution in USD files or implement user prompts/authorization before executing embedded scripts. Avoid opening untrusted or unverified USD files from unknown sources.
Nvidia Isaac Sim 2022.2.0, Omniverse Audio2face 2022.2, Omniverse Code 2022.3.0, Omniverse Create 2022.3, Omniverse Machinima 2022.3, Omniverse View 2022.2.1
- 1. Identify which Omniverse application(s) are currently installed from the affected list: Isaac Sim, Audio2Face, Code, Create, Machinima, or View
- 2. For each affected application, determine the currently installed version
- 3. Download or access the corresponding fixed version from the NVIDIA website or your distribution channel: Isaac Sim 2022.2.0 or later, Audio2Face 2022.2 or later, Code 2022.3.0 or later, Create 2022.3 or later, Machinima 2022.3 or later, View 2022.2.1 or later
- 4. Back up any custom USD files, settings, and projects before upgrading
- 5. Install the fixed version of each affected Omniverse application
- 6. After upgrading, verify that USD files with embedded Python code are no longer automatically executed when opened
- 7. Educate users to avoid opening untrusted USD files from unknown sources
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42268 — 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-2022-42268 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