CVE-2026-24132

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.7% (54th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-3783 (ENISA EUVD) · GHSA-f456-rf33-4626 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Orval generates type-safe JS clients (TypeScript) from any valid OpenAPI v3 or Swagger v2 specification. Versions 7.19.0 and below and 8.0.0-rc.0 through 8.0.2 allow untrusted OpenAPI specifications to inject arbitrary TypeScript/JavaScript into generated mock files via the const keyword on schema properties. These const values are interpolated into the mock scalar generator (getMockScalar in packages/mock/src/faker/getters/scalar.ts) without proper escaping or type-safe serialization, which results in attacker-controlled code being emitted into both interface definitions and faker/MSW handlers. The vulnerability is similar in impact to the previously reported enum x-enumDescriptions (GHSA-h526-wf6g-67jv), but it affects a different code path in the faker-based mock generator rather than @orval/core. The issue has been fixed in versions 7.20.0 and 8.0.3.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
54th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 23, 2026

Last Modified

June 17, 2026

Advisory Details (9)

Auto-updated Nov 1, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)

Orval Mock Generation Code Injection via const · Advisory · orval-labs/orval · GitHub

https://github.com/orval-labs/orval/security/advisories/GHSA-f456-rf33-4626
GitHub release Patch Available

Release v8.0.3

Patch available: orval-labs/orval v8.0.3

https://github.com/orval-labs/orval/releases/tag/v8.0.3
GitHub release Patch Available

Release v7.20.0

Patch available: orval-labs/orval v7.20.0

https://github.com/orval-labs/orval/releases/tag/v7.20.0
GitHub pull request Patch Available

fix(mock): CVE-2026-24132 escape mocked values

Patch available: orval-labs/orval v8.17.0 (PR #2830 merged 2026-01-22)

https://github.com/orval-labs/orval/pull/2830
GitHub pull request

fix(mock): v7 escape mocked values

Fix merged in orval-labs/orval PR #2829 on 2026-01-22 — awaiting tagged release

https://github.com/orval-labs/orval/pull/2829
GitHub pull request Patch Available

fix(mock): escape mocked values

Patch available: orval-labs/orval v8.17.0 (PR #2828 merged 2026-01-22)

https://github.com/orval-labs/orval/pull/2828
GitHub commit Patch Available

commit 9b211cddc9f0 (orval-labs/orval)

Patch available: orval-labs/orval v8.17.0 (contains commit 9b211cddc9f0)

https://github.com/orval-labs/orval/commit/9b211cddc9f009f8a671e4ac5c6cb72cd8646b62
GitHub commit

commit 6d8ece07ccb8 (orval-labs/orval)

Fix landed in orval-labs/orval commit 6d8ece07ccb8 — awaiting tagged release

https://github.com/orval-labs/orval/commit/6d8ece07ccb80693ad43edabccb3957aceadcd06
GitHub commit Patch Available

commit 44ca8c1f5f93 (orval-labs/orval)

Patch available: orval-labs/orval v8.17.0 (contains commit 44ca8c1f5f93)

https://github.com/orval-labs/orval/commit/44ca8c1f5f930a3e4cefb6b79b38bcde7f8532a5

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@orval/mock @ 8.0.3 (fixes >= 8.0.0-rc.0, < 8.0.3)—ghsa
npm@orval/mock @ 7.20.0 (fixes < 7.20.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@orval/mock—
  • every version up to 7.20.0: fixed in 7.20.0
  • 8.0.0-rc.0 up to 8.0.3: fixed in 8.0.3
—

Weakness Classification(2)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 227 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 128 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 08:37 UTCEG score recompute
  2. 2026-11-02 08:36 UTCGHSA enrichmentGHSA-f456-rf33-4626 · GitHub severity HIGH
  3. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  4. 2026-11-01 10:22 UTCGHSA enrichmentGHSA-f456-rf33-4626 · GitHub severity HIGH
  5. 2026-11-01 07:57 UTCGHSA enrichmentGHSA-f456-rf33-4626 · GitHub severity HIGH
  6. 2026-11-01 07:57 UTCEG score recompute
  7. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  8. 2026-10-31 12:07 UTCEG score recompute
  9. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  10. 2026-10-30 13:51 UTCEG score recompute
  11. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  12. 2026-10-28 17:05 UTCEG score recompute
  13. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  14. 2026-10-27 18:51 UTCEG score recompute
  15. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  16. 2026-10-26 20:37 UTCEG score recompute
  17. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  18. 2026-10-25 20:29 UTCEG score recompute
  19. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  20. 2026-10-25 14:41 UTCEG score recompute
  21. 2026-10-24 22:14 UTCEG score recompute
  22. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  23. 2026-10-23 23:49 UTCEG score recompute
  24. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  25. 2026-10-23 01:33 UTCEG score recompute
Show 74 more
  1. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-10-22 03:04 UTCEG score recompute
  3. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-10-21 04:48 UTCEG score recompute
  5. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-10-20 06:33 UTCEG score recompute
  7. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  8. 2026-10-19 08:16 UTCEG score recompute
  9. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-10-18 03:54 UTCEG score recompute
  11. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-10-17 06:27 UTCEG score recompute
  13. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-10-16 07:52 UTCEG score recompute
  15. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  16. 2026-10-15 06:52 UTCEG score recompute
  17. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  18. 2026-10-14 02:37 UTCEG score recompute
  19. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  20. 2026-10-12 22:50 UTCEG score recompute
  21. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  22. 2026-10-12 16:20 UTCEG score recompute
  23. 2026-10-11 20:02 UTCEG score recompute
  24. 2026-10-11 17:15 UTCEG score recompute
  25. 2026-10-11 14:47 UTCEG score recompute
  26. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  27. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  28. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  29. 2026-10-09 09:55 UTCOSV refresh
  30. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  31. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  32. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  33. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  34. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  35. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  36. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  37. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  38. 2026-09-29 15:21 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  39. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  40. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  41. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  42. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  43. 2026-09-24 14:03 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  44. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  45. 2026-09-19 17:03 UTCOSV refresh
  46. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  47. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  48. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  49. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  50. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  51. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  52. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  53. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  54. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  55. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  56. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  57. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  58. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  59. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  60. 2026-08-31 20:34 UTCOSV refresh
  61. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  62. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  63. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  64. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  65. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  66. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  67. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  68. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  69. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  70. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  71. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  72. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  73. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  74. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.7% · 49th percentile

Frequently asked(5)

What is CVE-2026-24132?
CVE-2026-24132 is a critical-severity vulnerability; its CVE record was published on January 23, 2026. Orval generates type-safe JS clients (TypeScript) from any valid OpenAPI v3 or Swagger v2 specification. Versions 7.19.0 and below and 8.0.0-rc.0 through 8.0.2 allow untrusted OpenAPI specifications to inject arbitrary TypeScript/JavaScript into generated mock files via the const keyword on schema…
When was the CVE record for CVE-2026-24132 published?
The CVE record for CVE-2026-24132 was published on January 23, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-24132 actively exploited?
CVE-2026-24132 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-24132?
CVE-2026-24132 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-24132?
A fix for CVE-2026-24132 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-24132

Explore →

Is Your Infrastructure Affected by CVE-2026-24132?

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