Skip to content

Arbitrary code execution via Arazzo `$faker` expression using `respect`

High
tatomyr published GHSA-xw2f-5386-m542 Jul 27, 2026

Package

npm @redocly/cli (npm)

Affected versions

< 2.33.0

Patched versions

2.33.0
npm @redocly/respect-core (npm)
<2.33.0 <1.34.17
>=2.33.0 >=1.34.17

Description

Impact

A malicious Arazzo description could run arbitrary code on the machine of anyone
who runs the respect command against it — including shell command execution and
theft of CI secrets. Only users who run the respect command on a description
they did not author (third-party, fetched, or pull-request content) are affected.
Users running their own workflows are not.

Patches

Fixed in @redocly/respect-core and @redocly/cli v2.33.0.

Workarounds

Do not run the respect command on Arazzo descriptions from untrusted or unreviewed sources.

To detect an exploit attempt, inspect the description's parameter and input
values for any string that begins with $faker. and contains constructor.

References

#2881

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVE ID

CVE-2026-63325

Weaknesses

Improper Control of Generation of Code ('Code Injection')

The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Learn more on MITRE.

Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. eval). Learn more on MITRE.

Credits