# CVE-2026-63225: Redocly CLI: Path traversal when using `split` command

> Attackers can use crafted OpenAPI or AsyncAPI files to write or overwrite files outside the intended output directory via the split command.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-657c-g7qc-r9j2

## What is CVE-2026-63225?

CVE-2026-63225 is a medium-severity path traversal vulnerability in redocly-cli, published on 16 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Redocly CLI makes OpenAPI validation, linting, and documentation workflows easier. Prior to @redocly/cli 2.33.2, the split command constructs output paths under --outDir from untrusted OpenAPI or AsyncAPI component names and x-codeSamples lang values without verifying that the resolved target remains inside the selected directory. A description containing literal ../ traversal segments in those fields can cause the split command to place or overwrite files outside --outDir. Component data remains constrained to YAML or JSON, and code-sample filenames remain based on the HTTP method, so this is not an unrestricted arbitrary-content file write. This issue is fixed in @redocly/cli version 2.33.2.

Weakness: CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-63225?

4 open source packages ship an affected version, including @redocly/cli.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@redocly/cli` | npm | All versions | 1.34.17 |
| `@redocly/cli` | npm | All versions | 1.34.17 |
| `@redocly/cli` | npm | From 2.0.0 | 2.33.2 |
| `@redocly/cli` | npm | From 2.0.0 | 2.33.2 |

## How do I fix CVE-2026-63225?

Upgrade @redocly/cli to a fixed version for your release line: 1.34.17 or 2.33.2.

## Is CVE-2026-63225 being exploited?

There is no known exploitation of CVE-2026-63225 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63225 and fix it if it is affected.

What it is: CVE-2026-63225 is a medium-severity path traversal vulnerability in redocly-cli, published on 16 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-63225 in the wild and no public exploit code.

Affected packages and fixed versions:
- @redocly/cli (npm): affected all versions; fixed in 1.34.17
- @redocly/cli (npm): affected all versions; fixed in 1.34.17
- @redocly/cli (npm): affected from 2.0.0; fixed in 2.33.2
- @redocly/cli (npm): affected from 2.0.0; fixed in 2.33.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-63225/ (Markdown: https://insights.sbomify.com/CVE-2026-63225/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-63225
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-63225
- OSV: https://osv.dev/vulnerability/CVE-2026-63225

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-63225/
Summaries are generated and may contain mistakes; the official description above is the record.