How severe is GHSA-w5fx-fh39-j5rw?

No CVSS score has been assigned to GHSA-w5fx-fh39-j5rw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w5fx-fh39-j5rw?

GHSA-w5fx-fh39-j5rw affects the following packages: @openai/codex (npm). Ecosystems affected: npm.

How do I fix GHSA-w5fx-fh39-j5rw?

Update @openai/codex to 0.39.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w5fx-fh39-j5rw is resolved across your whole dependency graph.

How do I detect GHSA-w5fx-fh39-j5rw in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openai/codex, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-w5fx-fh39-j5rw 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-w5fx-fh39-j5rw?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w5fx-fh39-j5rw can be triaged on real exposure rather than presence alone.

Is GHSA-w5fx-fh39-j5rw actively exploited in the wild?

No public exploit code has been indexed for GHSA-w5fx-fh39-j5rw 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.

What is the EPSS score for GHSA-w5fx-fh39-j5rw?

GHSA-w5fx-fh39-j5rw has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 57th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-w5fx-fh39-j5rw?

GHSA-w5fx-fh39-j5rw is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w5fx-fh39-j5rw published, and has it been updated?

GHSA-w5fx-fh39-j5rw was published on September 19, 2025 and was last updated on September 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-w5fx-fh39-j5rw — @openai/codex

Fix: openai/codex@8595237

GHSA-w5fx-fh39-j5rw is a Improper Input Validation vulnerability in @openai/codex. A fix is available for @openai/codex — see the affected versions and patch details below.

Codex has sandbox bypass due to bug in path configuration logic

Also known asCVE-2025-59532

Published

Sep 19, 2025

Updated

Sep 22, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-w5fx-fh39-j5rw.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

236other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@openai/codexnpm

16.1Mdownloads / week

Description

Due to a bug in the sandbox configuration logic, Codex CLI could treat a model-generated cwd as the sandbox’s writable root, including paths outside of the folder where the user started their session.

This logic bypassed the intended workspace boundary and enables arbitrary file writes and command execution where the Codex process has permissions - this did not impact the network-disabled sandbox restriction.

Remediation We released a patch in Codex CLI 0.39.0 that canonicalizes and validates that the boundary used for sandbox policy is based on where the user started the session, and not the one generated by the model. Users running 0.38.0 or earlier should update immediately via their package manager or by reinstalling the latest Codex CLI to ensure sandbox boundaries are enforced.

If using the Codex IDE extension, users should immediately update to 0.4.12 for a fix of the sandbox issue.

Thank you to Tzanko Matev (Codetracer) for reporting the issue!

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@openai/codex`	≥ 0.2.0&&< 0.39.0	0.39.0`npm install @openai/codex@0.39.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @openai/codex, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @openai/codex to 0.39.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w5fx-fh39-j5rw 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w5fx-fh39-j5rw can be triaged on real exposure rather than presence alone.

Tailored to GHSA-w5fx-fh39-j5rw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Due to a bug in the sandbox configuration logic, Codex CLI could treat a model-generated `cwd` as the sandbox’s writable root, including paths outside of the folder where the user started their session. This logic bypassed the intended workspace boundary and enables arbitrary file writes and command execution where the Codex process has permissions - this did not impact the network-disabled sandbox restriction. **Remediation** We released a patch in Codex CLI **0.39.0** that canonicalizes and validates that the boundary used for sandbox policy is based on where the user started the session,

O3 Security · Impact-Aware SCA

Is GHSA-w5fx-fh39-j5rw in your dependencies?

O3 Security finds GHSA-w5fx-fh39-j5rw across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works