CVE-2026-132224

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-129010 (ENISA EUVD) · GHSA-xr6g-wr3x-r365 (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan mitigationThe upstream fix is not in a release yet: until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high, then apply it (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

Optimizely Web Experimentation before 2026-11-17 mishandles the account signup flow, leading to presence of attacker-controlled code in the projectJS (aka Project JavaScript) field of certain cdn.optimizely.com assets.

CVSS
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
47
EG Risk 47/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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: An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high, then apply it.
EPSS PROB
0.4%
EPSS %ILE
36th
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 (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-20). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.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; Attend at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Until the release ships, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high, then apply it.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

November 18, 2026

Last Modified

November 21, 2026

Advisory Details (10)

Auto-updated Nov 18, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
Web page

Hundreds of websites deliver potent malware cocktail to unsuspecting visitors - Ars Technica

https://arstechnica.com/security/2026/11/malicious-code-delivered-through-optimizely-hits-visitors-to-hundreds-of-sites/
Web page

Attackers Used Optimizely to A/B Test Malware on Top Websites – Krebs on Security

https://krebsonsecurity.com/2026/11/attackers-used-optimizely-to-a-b-test-malware-on-top-websites/
Web page

The BBC and CNN were loading Optimizely without consent six weeks before it was turned against their visitors — That Privacy Guy!

https://www.thatprivacyguy.com/blog/optimizely-bbc-cnn-consent/
Web page

Optimizely compromised, served malware on Zoom, GitLab | Hacker News

https://news.ycombinator.com/item?id=50524767
GitHub pull request

Add optimizely.js resource

Fix merged in brave/adblock-resources PR #355 on 2026-11-17 — awaiting tagged release

https://github.com/brave/adblock-resources/pull/355
Web page

Reflecting on the Optimizely Incident and Why We Keep Failing

https://scotthelme.co.uk/reflecting-on-the-optimizely-incident-and-why-we-keep-failing/
Web page

World's Largest Brands Infected With Malware Via Optimizely

https://blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/
Web page

Optimizely Service Status - Web Experimentation Security Incident

https://status.optimizely.com/incidents/ftw0fh9wx43z

Vendor Advisories for CVE-2026-132224(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 9× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-11-21 05:28 UTCEchelonGraph re-scored
  3. 2026-11-21 05:28 UTCGHSA enrichmentGHSA-xr6g-wr3x-r365 · GitHub severity HIGH
  4. 2026-11-21 04:21 UTCEchelonGraph re-scored
  5. 2026-11-21 04:21 UTCGHSA enrichmentGHSA-xr6g-wr3x-r365 · GitHub severity HIGH
  6. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  7. 2026-11-20 01:30 UTCEchelonGraph re-scored
  8. 2026-11-20 01:30 UTCGHSA enrichmentGHSA-xr6g-wr3x-r365 · GitHub severity HIGH
  9. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-11-18 18:46 UTCGHSA enrichmentGHSA-xr6g-wr3x-r365 · GitHub severity HIGH
  11. 2026-11-18 18:29 UTCEchelonGraph re-scored
  12. 2026-11-18 17:23 UTCEchelonGraph re-scored
  13. 2026-11-18 17:03 UTCENISA EUVD ID recordedEUVD-2026-129010 · Source: ENISA EUVD
  14. 2026-11-18 16:28 UTCEchelonGraph re-scored
  15. 2026-11-18 15:53 UTCEchelonGraph re-scoredFirst assessed: 7.1 HIGH
  16. 2026-11-18 15:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-132224?
CVE-2026-132224 is a high-severity vulnerability; its CVE record was published on November 18, 2026. Optimizely Web Experimentation before 2026-11-17 mishandles the account signup flow, leading to presence of attacker-controlled code in the projectJS (aka Project JavaScript) field of certain cdn.optimizely.com assets.
When was the CVE record for CVE-2026-132224 published?
The CVE record for CVE-2026-132224 was published on November 18, 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 November 21, 2026; the record at its source may have been updated since.
Is CVE-2026-132224 actively exploited?
CVE-2026-132224 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-132224?
CVE-2026-132224 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-132224?
An upstream fix for CVE-2026-132224 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-132224 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-132224?

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