VulnerabilityPublished 20 Sep 2026Updated 26 Oct 2026

CVE-2026-63225: Redocly CLI · Path traversal when using `split` command

Affects redocly-cliSource GCVE Database

Authoritative record:CVE-2026-63225· Medium 4.4

Not known to be exploited · CVSS 4.4 Medium : upgrade to 2.33.2 when convenient.

Data as of 26 Oct 2026, 19:42 UTC

CVSS 3.1 base score

4.4Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 2.33.2

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade redocly-cli to 2.33.2.

Affected software

Product	Affected	Fixed in
Homebrewredocly-cli`pkg:brew/redocly-cli`Other threats	Affected >=1.27.2 <2.33.2	Fixed in 2.33.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Redocly CLI version 2.33.2. Users should upgrade to this version to remediate the vulnerability. As a workaround, do not run the `split` command on API descriptions from untrusted or unreviewed sources. To detect exploitation attempts, inspect component names and `x-codeSamples` `lang` values for literal `../` path traversal sequences, which are not legitimate in these fields.

Description

A path traversal vulnerability exists in Redocly CLI's `split` command that allows an attacker to cause files to be written outside the intended output directory. This occurs when processing malicious OpenAPI or AsyncAPI descriptions. The attacker’s control over file names and contents is limited, as files are emitted only as YAML/JSON and code-sample files are named after HTTP methods. The issue affects versions from 1.27.2 up to but not including 2.33.2 and is fixed in version 2.33.2.

Impact

An attacker who provides a malicious API description to the `split` command can cause files to be written outside the intended directory on the victim’s machine. This could lead to limited unauthorized file overwrite or placement, potentially impacting system integrity or availability. The attacker’s control over file names and contents is restricted, reducing the severity of potential impact. No confidentiality impact is indicated.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 19:42 UTC

Technical details

References

Community reviews

Related threats