A critical security vulnerability affecting Optimizely Web Experimentation has been identified and linked to active exploitation occurring on the same day as its public disclosure. The flaw, tracked as CVE-2026-132224, was officially reserved and published on November 18, 2026. According to available tracking data, the vulnerability was flagged as being actively exploited in the wild on that same date.
The identification of this exploit relies on a single commercial vulnerability intelligence source, the VulnCheck Known Exploited Vulnerabilities (KEV) catalog, which listed the flaw on November 18. Currently, other major repositories, including the United States Cybersecurity and Infrastructure Security Agency (CISA) KEV and the European Union Agency for Cybersecurity (ENISA) EUVD, do not include this vulnerability in their respective lists of exploited threats. Because the evidence is derived from a single source, the claim of active exploitation remains uncorroborated by broader industry or government databases at this time.
The vulnerability is categorized as a third-party risk associated with the Optimizely platform. While the specific technical mechanics of the flaw are currently being analyzed by security researchers, the initial report regarding the exploitation was documented on November 18, 2026. This report serves as the primary basis for the assertion that the vulnerability was leveraged by malicious actors immediately following its disclosure.
The CVSS severity score for CVE-2026-132224 is currently listed as not yet determined, and the Exploit Prediction Scoring System (EPSS) places the vulnerability at a 0.41% probability of exploitation, ranking it in the 36.1st percentile. These metrics suggest that while the vulnerability is significant enough to warrant tracking, it does not currently carry the highest possible risk rating assigned to more widespread or easily weaponized flaws.
Optimizely has not yet provided a detailed public statement confirming the specific scope of the impact or the nature of the unauthorized access associated with this exploit. The lack of secondary confirmation from government agencies or additional threat intelligence aggregators means that the full extent of the exploitation remains unverified by the affected vendor.
Organizations utilizing the Optimizely Web Experimentation product are advised to monitor official security advisories from the vendor for patches or mitigation instructions. Given the reported timeline of the exploit, users should prioritize reviewing their system logs for any anomalous activity that may have occurred on or after November 18.
As this situation develops, further technical documentation is expected to emerge from security researchers who are currently investigating the third-party dependencies involved. Until such time as the vendor or official cybersecurity authorities provide comprehensive guidance, the vulnerability should be treated with caution, particularly by those managing sensitive experimentation data or integrated web environments.






