Skip to main content
VulnerabilityPublished

CVE-2025-55345: JFROG · UNIX Symbolic Link (Symlink) Following

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Avoid running Codex CLI in workspace-write mode on untrusted or unverified repositories or directories.
  2. Implement strict validation and sanitization of workspace contents before executing Codex CLI, including scanning for suspicious or unexpected symbolic links.
  3. Use filesystem permissions and access controls to limit the ability of Codex CLI processes to write outside designated directories, such as running the tool inside sandboxed or containerized environments with restricted filesystem access.
  4. Monitor and audit file system changes during Codex CLI operations to detect unauthorized file overwrites.
  5. Employ runtime security tools that can detect and block attempts to follow symlinks outside allowed paths or prevent unauthorized file modifications.
  6. Stay updated with vendor advisories for patches or updates addressing this vulnerability and apply them promptly once available.
  7. Educate developers and DevOps teams about the risks of symlink attacks and safe usage practices for Codex CLI.
  8. Consider implementing integrity verification for critical files that could be targeted by this vulnerability to detect tampering early.

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.

References

Community reviews

Loading reviews…