GHSA-657c-g7qc-r9j2 is a medium-severity (CVSS 4.4) Path Traversal vulnerability in @redocly/cli. A fix is available for @redocly/cli — see the affected versions and patch details below.
Redocly CLI: Path traversal when using `split` command
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-657c-g7qc-r9j2.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-657c-g7qc-r9j2 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 374,847 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
@redocly/cli📦@redocly/cliReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
Impact
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.
Patches
Fixed in @redocly/cli v2.33.2.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @redocly/cli | all versions | 1.34.17npm install @redocly/cli@1.34.17 |
| 📦npm | @redocly/cli | ≥ 2.0.0&&< 2.33.2 | 2.33.2npm install @redocly/cli@2.33.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @redocly/cli, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @redocly/cli to 1.34.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-657c-g7qc-r9j2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-657c-g7qc-r9j2 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-657c-g7qc-r9j2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-657c-g7qc-r9j2 in your dependencies?
O3 Security finds GHSA-657c-g7qc-r9j2 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.