Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.4amended

Redocly CLI: Path traversal when using split command

CVE-2026-63225GHSA-657c-g7qc-r9j2

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@redocly/cli 2.33.2, 1.34.17), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @redocly/cli

    Affected
    < 1.34.17>= 2.0.0, < 2.33.2
    Fixed in
    1.34.17, 2.33.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.4 · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
EPSS
  • CVE-2026-63225: 0.18% estimated exploitation activity in the next 30 days; percentile 7.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-657c-g7qc-r9j2

  2. Revision 2 · amended ·

    Amended from osv record GHSA-657c-g7qc-r9j2

  3. Revision 1 · created ·

    Published from ghsa record GHSA-657c-g7qc-r9j2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-63225

Advisory: Redocly CLI: Path traversal when using `split` command
IDs: CVE-2026-63225, GHSA-657c-g7qc-r9j2
Record: https://patchnext.com/advisories/cve-2026-63225 (revision 3, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @redocly/cli 2.33.2, 1.34.17. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @redocly/cli: affected < 1.34.17; >= 2.0.0, < 2.33.2; fixed in 1.34.17, 2.33.2

## Suggested inspection (read-only)
- `npm ls @redocly/cli --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @redocly/cli.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-657c-g7qc-r9j2 (GitHub-reviewed advisory GHSA-657c-g7qc-r9j2 lists affected ranges: npm @redocly/cli >=0 =2.0.0 <2.33.2)
- Verified: https://osv.dev/vulnerability/GHSA-657c-g7qc-r9j2 (OSV record GHSA-657c-g7qc-r9j2 lists affected ranges: npm @redocly/cli >=0 =2.0.0 <2.33.2 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…