CVE-2026-63225 json
Redocly CLI: Path traversal when using `split` command
published 3mo ago modified last mo. also EUVD-2026-81013 , GHSA-657c-g7qc-r9j2
- cvss
- 4.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm @redocly/cli 1.34.17, 2.33.2
- github.com/Redocly/redocly-cli@26a0f29 commit
- github.com/Redocly/redocly-cli@5041204 commit
- github.com/Redocly/redocly-cli#2891 pull request
- github.com/Redocly/redocly-cli#2923 pull request
- github.com/Redocly/redocly-cli/releases/tag/@redocly/cli@1.34.17 release
- github.com/Redocly/redocly-cli/releases/tag/@redocly/cli@2.33.2 release
Is CVE-2026-63225 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L |
| GitHub | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @redocly/cli | <1.34.17 >=2.0.0, <2.33.2 |
1.34.17 2.33.2 |
Affected products
- Redocly redocly-cli
Classification
References
-
github.com
/Redocly/redocly-cli/pull/2891
web
-
github.com
/Redocly/redocly-cli/pull/2923
web
-
github.com
/Redocly/redocly-cli/commit/26a0f299fae0b3bb7bd513043d2f1e90e69f79ee
web
-
github.com
/Redocly/redocly-cli/commit/504120419a72b5c684471478337ee3b45d8bfad3
web
-
github.com
/Redocly/redocly-cli/security/advisories/GHSA-657c-g7qc-r9j2
web, advisory
-
github.com
/Redocly/redocly-cli/releases/tag/@redocly/cli@1.34.17
web
-
github.com
/Redocly/redocly-cli/releases/tag/@redocly/cli@2.33.2
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-63225
advisory
-
github.com
/Redocly/redocly-cli
package
Sources
- CVE List CVE-2026-63225
- GitHub Advisory GHSA-657c-g7qc-r9j2
- NVD CVE-2026-63225
- Maintainer advisory GHSA-657c-g7qc-r9j2
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of Redocly/redocly-cli published their own advisory on GitHub. Reviewed sources take precedence over it.