Loading
Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: < 1.34.17
Patched in 1.34.17
Vulnerable: >= 2.0.0, < 2.33.2
Patched in 2.33.2
Details
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.
Fixed in @redocly/cli v2.33.2.
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.
EPSS, exploit probability
Low0.18%
estimated chance of real-world exploitation in the next 30 days, higher than 7.5% of every CVE FIRST.org scores
Refreshed 11/1/2026, via FIRST.org's EPSS model, not CVSS, this measures likelihood of exploitation, not how severe it would be.
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.