Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-63225 medium CVSS 4.4

Path Traversal in @redocly/cli (CVE-2026-63225)

Summary

Path traversal in @redocly/cli (CVE-2026-63225). Risk of unauthorized operations or information disclosure. Exploitable via split. Mitigation: upgrade to 2.33.2 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-63225 has been found in @redocly/cli.
Attackers can target a specific entry point like split over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.4/10.
What to do: upgrade @redocly/cli to 2.33.2 or later.
If unsure, ask your IT team or search "@redocly/cli CVE-2026-63225" on the vendor's site.

CVE-2026-63225 (@redocly/cli) — CWE-22 / CVSS v3 4.4
Attack vector: local / unauthenticated
Attack surface: split / lang
Patched: 2.33.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in @redocly/cli. Attackers reach the vulnerable code path via split without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @redocly/cli. Attack surface: split / lang.

🔥 Severity

Severity: Medium (CVSS 4.4/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.33.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@redocly/cli' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@redocly/cli' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @redocly/cli を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @redocly/cli to 2.33.2

    ステージング環境で 2.33.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @redocly/cli
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.33.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details