CVE-2026-63325

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Redocly CLI makes OpenAPI validation, linting, and documentation workflows easier. Prior to version 2.33.0 of @redocly/respect-core and @redocly/cli, the respect command dynamically evaluates $faker runtime expressions in Arazzo descriptions. A crafted expression can traverse constructor, prototype, or __proto__ properties in packages/respect-core/src/modules/context-parser/get-value-from-context.ts, reach the JavaScript Function constructor, and execute arbitrary code when a user processes an untrusted description. 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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

Arbitrary code execution via Arazzo `$faker` expression using `respect` · Advisory · Redocly/redocly-cli · GitHub

https://github.com/Redocly/redocly-cli/security/advisories/GHSA-xw2f-5386-m542
github_pr Patch Available

fix: fix $faker expression code execution vulnerablility

Patch available: Redocly/redocly-cli @redocly/[email protected] (PR #2922 merged 2026-06-30)

https://github.com/Redocly/redocly-cli/pull/2922
github_pr Patch Available

fix: respect arbitrary code execution via $faker runtime expression

Patch available: Redocly/redocly-cli @redocly/[email protected] (PR #2881 merged 2026-06-15)

https://github.com/Redocly/redocly-cli/pull/2881
github_commit Patch Available

commit d26d45236806 (Redocly/redocly-cli)

Patch available: Redocly/redocly-cli @redocly/[email protected] (contains commit d26d45236806)

https://github.com/Redocly/redocly-cli/commit/d26d452368066be1400f43cea915dd9ea508e18b

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 18:34 UTCEG score recompute
  4. 2026-09-18 05:42 UTCEG score recompute
  5. 2026-09-16 19:24 UTCEG score recompute
  6. 2026-09-16 19:15 UTCEG score recompute
  7. 2026-09-16 19:14 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-63325?
CVE-2026-63325 is a high vulnerability published on September 16, 2026. Redocly CLI makes OpenAPI validation, linting, and documentation workflows easier. Prior to version 2.33.0 of @redocly/respect-core and @redocly/cli, the respect command dynamically evaluates $faker runtime expressions in Arazzo descriptions. A crafted expression can traverse constructor,…
When was CVE-2026-63325 disclosed?
CVE-2026-63325 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63325 actively exploited?
CVE-2026-63325 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.6% of all scored CVEs.
What is the CVSS score of CVE-2026-63325?
CVE-2026-63325 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-63325?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63325, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-63325

Explore →

Is Your Infrastructure Affected by CVE-2026-63325?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs