CVE-2026-63225

Redocly CLI: Path traversal when using split command

Workarounds

Do not run the split command on API descriptions from untrusted or unreviewed sources.

To detect an exploit attempt, inspect the description's component names and
x-codeSamples lang values for a literal ../, neither legitimately contains
path segments.

An OpenAPI or AsyncAPI description could make the split command write
files outside the chosen output directory, on the machine of anyone who runs
split against it. The write is constrained rather than a free file-write
primitive: component data is emitted only as YAML/JSON, and code-sample files are
named after the HTTP method, so an attacker can place or overwrite files at an
unintended path but has limited control over their name and contents.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-63225 has a CVSS score of 4.4 (Medium). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.34.17, 2.33.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Fixed in @redocly/cli v2.33.2.

1. What is CVE-2026-63225? CVE-2026-63225 is a medium-severity path traversal vulnerability in @redocly/cli (npm), affecting versions < 1.34.17. It is fixed in 1.34.17, 2.33.2. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-63225? CVE-2026-63225 has a CVSS score of 4.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @redocly/cli are affected by CVE-2026-63225? @redocly/cli (npm) versions < 1.34.17 is affected.
4. Is there a fix for CVE-2026-63225? Yes. CVE-2026-63225 is fixed in 1.34.17, 2.33.2. Upgrade to this version or later.
5. Is CVE-2026-63225 exploitable, and should I be worried? Whether CVE-2026-63225 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-63225 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-63225?
   • Upgrade @redocly/cli to 1.34.17 or later
   • Upgrade @redocly/cli to 2.33.2 or later