How severe is GHSA-grjp-54v3-c442?

No CVSS score has been assigned to GHSA-grjp-54v3-c442 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-grjp-54v3-c442?

GHSA-grjp-54v3-c442 affects the following packages: usd-core (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-grjp-54v3-c442?

Update usd-core to 25.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-grjp-54v3-c442 is resolved across your whole dependency graph.

How do I detect GHSA-grjp-54v3-c442 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for usd-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-grjp-54v3-c442 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-grjp-54v3-c442?

O3 pinpoints whether GHSA-grjp-54v3-c442 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-grjp-54v3-c442 actively exploited in the wild?

No public exploit code has been indexed for GHSA-grjp-54v3-c442 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-grjp-54v3-c442 published, and has it been updated?

GHSA-grjp-54v3-c442 was published on October 29, 2025 and was last updated on October 29, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-grjp-54v3-c442

OpenUSD File Parsing Use-After-Free Remote Code Execution Vulnerability

Published

Oct 29, 2025

Updated

Oct 29, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐍usd-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Patch

This is fixed with commit b953092, with the fix available in OpenUSD 25.11 and onwards.

Summary

We have been advised by Zero Day Initiative that our usage of the USD framework may constitute a Use-After-Free Remote Code Execution Vulnerability. They have sent us the attached file illustrating the issue. Indeed, we see a use after free exception when running the file through our importer with an address sanitizer.

zdi-23709-poc0.zip

Thanks in advance.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`usd-core`	all versions	25.11

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for usd-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update usd-core to 25.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-grjp-54v3-c442 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-grjp-54v3-c442 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-grjp-54v3-c442. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

# Patch This is fixed with [commit b953092](https://github.com/PixarAnimationStudios/OpenUSD/commit/b9530922b6a8ea72cd43661226b693fff8abbe4c), with the fix available in OpenUSD 25.11 and onwards. # Summary We have been advised by Zero Day Initiative that our usage of the USD framework may constitute a Use-After-Free Remote Code Execution Vulnerability. They have sent us the attached file illustrating the issue. Indeed, we see a use after free exception when running the file through our importer with an address sanitizer. [zdi-23709-poc0.zip](https://github.com/user-attachments/files/17474297

O3 Security · Impact-Aware SCA

Is GHSA-grjp-54v3-c442 in your dependencies?

O3 detects GHSA-grjp-54v3-c442 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works