CVE-2026-132224: Optimizely Web Experimentation · External Control of Critical State Data
Affects Optimizely Web ExperimentationSource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 2026-11-17 soon.
Data as of 18 Nov 2026, 16:06 UTC
Thin evidence
One scorer or none| CNA (mitre) | CVSS 4.0 | 7.1 |
|---|
- Patch
- Available – fixed in 2026-11-17
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade Optimizely Web Experimentation to 2026-11-17.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OptimizelyWeb Experimentation | Affected
| Fixed in
|
AI-suggested
A fix for this vulnerability is available in Optimizely Web Experimentation version 2026-11-17. Users and administrators should upgrade to this version or later to remediate the issue. Since this is not a cloud service, manual patching is required. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-132224 is a high-severity vulnerability in Optimizely Web Experimentation affecting versions before 2026-11-17. It involves improper handling of the account signup flow, which allows attacker-controlled code to be injected into the projectJS field of certain cdn.optimizely.com assets. This flaw is categorized under CWE-642, External Control of Critical State Data. The vulnerability has been fixed as of version 2026-11-17.
References
- pages.optimizely.com/rs/947-RKE-048/images/Security%20Incident%20Report%20-%20Optimizely%20Web%20Experimentation%20-%20Nov%2017%202026.pdf (opens in a new tab)
- status.optimizely.com/incidents/ftw0fh9wx43z (opens in a new tab)
- blog.report-uri.com/worlds-largest-brands-infected-with-malware-via-optimizely/ (opens in a new tab)
- scotthelme.co.uk/reflecting-on-the-optimizely-incident-and-why-we-keep-failing/ (opens in a new tab)
- github.com/brave/adblock-resources/pull/355 (opens in a new tab)
- news.ycombinator.com/item?id=50524767 (opens in a new tab)
- thatprivacyguy.com/blog/optimizely-bbc-cnn-consent/ (opens in a new tab)
- krebsonsecurity.com/2026/11/attackers-used-optimizely-to-a-b-test-malware-on-top-websites/ (opens in a new tab)
- bleepingcomputer.com/news/security/optimizely-supply-chain-attack-delivers-malware-to-cnn-fox-news-bbc-salesforce-sites/ (opens in a new tab)
- arstechnica.com/security/2026/11/malicious-code-delivered-through-optimizely-hits-visitors-to-hundreds-of-sites/ (opens in a new tab)
- therecord.media/optimizely-malicious-code-customer-sites (opens in a new tab)