PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-63325 Redocly CVE debrief

The Redocly CLI vulnerability allows code execution via crafted OpenAPI descriptions. This issue arises from the dynamic evaluation of $faker runtime expressions in Arazzo descriptions, which can traverse constructor, prototype, or __proto__ properties and execute arbitrary code. Users processing only trusted, self-authored workflows are not affected. The vulnerability is fixed in @redocly/respect-core and @redocly/cli version 2.33.0. Redocly CLI vulnerability allows code execution via crafted OpenAPI descriptions

Vendor
Redocly
Product
redocly-cli
CVSS
HIGH 7.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-16
Original CVE updated
2026-09-18
Advisory published
2026-09-16
Advisory updated
2026-09-18

Who should care

Users of Redocly CLI, especially those processing untrusted workflows, should assess exposure and upgrade to version 2.33.0. CI/CD pipeline maintainers and security teams should verify usage and monitor for suspicious activity.

Why it matters

CVE-2026-63325 in Redocly CLI poses a high risk due to potential code execution via crafted OpenAPI descriptions. Users of untrusted workflows should upgrade to version 2.33.0 and verify trust boundaries.

  • Code execution with CLI process privileges
  • Potential theft of CI secrets or sensitive data
  • Execution of shell commands via crafted OpenAPI descriptions
  • Verification of workflow trust boundaries and user input validation

Technical summary

The Redocly CLI vulnerability allows for code execution via crafted OpenAPI descriptions in versions prior to 2.33.0 of @redocly/respect-core and @redocly/cli. The issue arises from the dynamic evaluation of $faker runtime expressions in Arazzo descriptions, which can traverse constructor, prototype, or __proto__ properties and execute arbitrary code. The executed code runs with the privileges of the CLI process and can execute shell commands or read CI secrets. Users processing only trusted, self-authored workflows are not affected. This issue is fixed in @redocly/respect-core and @redocly/cli version 2.33.0. The vulnerability is fixed in @redocly/respect-core and @redocly/cli version 2.33.0.

Defensive priority

High priority for users of Redocly CLI with untrusted workflows

Recommended defensive actions

  • Upgrade to version 2.33.0 of @redocly/respect-core and @redocly/cli
  • Restrict usage of Redocly CLI to trusted workflows
  • Monitor for suspicious activity in CI environments
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in Redocly CLI versions prior to 2.33.0. The issue is fixed in version 2.33.0 of @redocly/respect-core and @redocly/cli. The executed code runs with the privileges of the CLI process and can execute shell commands or read CI secrets. Users processing only trusted, self-authored workflows are not affected.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-63325 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-63325

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-63325 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-63325

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.