The Exploit Bulletin — Tuesday, November 17, 2026: 3 issues require action
Tuesday, November 17, 2026 — 3 issues require action. If you run none of the software below, you are done.
Affects: Apache HTTP Server / mod_h2 from GitHub · Copeland XWEB EVO · Optimizely
1. Thread-safety race in Apache httpd mod_http2 assign_headers() gives unauthenticated remote code execution (CVE-2026-119618)
REMOTE CODE EXECUTION · CRITICAL · CVSS 8.1
VulnCheck added this flaw to its known-exploited catalog on 2026-11-15 and public exploit code exists, so an internet-facing httpd 2.4.55–2.4.70 with HTTP/2 enabled that is not upgraded is exposed to unauthenticated takeover of the server process.
A race condition in mod_http2's assign_headers() lets a worker thread write into memory owned by the connection thread through a shared lock-free allocator, corrupting the heap. A remote attacker who can reach a server with HTTP/2 (h2 or h2c) enabled can execute arbitrary commands as the server process without authentication; servers serving only HTTP/1.1 are not affected.
Affected: Apache HTTP Server 2.4.55 through 2.4.70 (HTTP/2 enabled via the Protocols directive); mod_h2 from GitHub 2.0.8 through 2.0.42; Red Hat Enterprise Linux 9 and 10 httpd mod_http2 packages (rated Important by Red Hat)
How to Test: Confirm the installed httpd version is between 2.4.55 and 2.4.70 (or mod_h2 2.0.8–2.0.42) and check whether the Protocols directive enables h2 or h2c; servers that only serve HTTP/1.1 are not vulnerable. On distro builds, check whether your vendor backported the 2.4.71 fix rather than relying on the version string. Review access and error logs for httpd worker crashes or heap-corruption segfaults coinciding with HTTP/2 connections, and treat an exposed, unpatched h2-enabled server as potentially compromised.
How to Patch: Upgrade to Apache HTTP Server 2.4.71 (released 2026-11-11) or the equivalent patched distribution package (Red Hat security bulletin RHSB-2026-017 covers RHEL 9 and 10). Until the upgrade is applied, remove h2 and h2c from the Protocols directive so the server serves only HTTP/1.1, which eliminates the vulnerable code path.
Evidence: VulnCheck KEV · Wiz analysis of CVE-2026-119618 unauthenticated RCE in mod_http2 · VulnCheck XDB public exploit for CVE-2026-119618
2. Pre-auth OS command injection via login username gives root on Copeland XWEB EVO controllers (CVE-2026-124002)
REMOTE CODE EXECUTION · CRITICAL · CVSS 9.3
VulnCheck's canary sensors recorded exploitation attempts on 2026-11-17 against a product that is end-of-service with no patch, so any XWEB EVO reachable from the internet that is not isolated now should be assumed compromised as root.
Shell metacharacters in the username field of login.lua, cleanout.lua or api.lua reach the OS before the password check, and the setuid-root wlua interpreter runs the injected commands as root, giving an unauthenticated attacker full control of the controller. The same advisory covers a hardcoded administrator backdoor password (CVE-2026-124004) in builds before 5.6.2.
Affected: Copeland (Dixell) XWEB EVO 5.2.3 up to but not including 5.7.0 (CVE-2026-124002); Copeland (Dixell) XWEB EVO before 5.6.2 (CVE-2026-124004, hardcoded administrator password)
How to Test: Read the firmware version from the XWEB EVO web interface: any 5.2.3 release below 5.7.0 is vulnerable to the command injection, and anything below 5.6.2 also carries the backdoor password. Review the controller's web-server logs for requests to login.lua, cleanout.lua or api.lua whose username parameter contains shell metacharacters (semicolons, pipes, backticks, $()), and check for unexpected processes, accounts, or administrator logins you did not make. The VulnCheck write-up contains a request-level proof of concept you can run against your own unit to confirm.
How to Mitigate: The product line reached end of service in March 2026 and VulnCheck reports no patch, so there is no fixed build to install. Take every XWEB EVO off any internet-facing network, restrict web access to trusted management hosts via firewall or VPN, change the administrator password where the hardcoded backdoor does not apply (5.6.2 and later), and plan replacement with a supported Copeland controller; check Copeland's System Software Updates page for any XWEB EVO build at 5.7.0 or later before assuming none exists.
Evidence: VulnCheck KEV · VulnCheck XDB exploit · Write-up with request-level PoC
3. Optimizely Web Experimentation snippets hijacked to serve card skimmer and iOS exploit
SUPPLY-CHAIN COMPROMISE · CRITICAL
Optimizely confirmed that malicious code was served through its customer snippets to at least 178 organizations' sites yesterday; teams that do not check their projects this week risk unreported card-skimming exposure and PCI notification failures.
Attackers abused a flaw in Optimizely's Experimentation account signup flow to inject malicious JavaScript into customer projects. The code was served to visitors of at least 178 organizations' websites, including Zoom, CNN, the BBC, Salesforce and GitLab. It swapped crypto wallet addresses, captured payment card details and, on iOS devices, loaded an exploit-kit second stage. Optimizely says it has fixed the flaw and removed the code.
Affected: Optimizely Web Experimentation customer snippets (served around 2026-11-16)
How to Test: Check whether your pages load cdn.optimizely.com snippets. Export each project's custom/shared code and change history from Nov 15–17 and look for unknown scripts or edits by unfamiliar collaborators. Search CSP reports and RUM/script-monitoring logs for unexpected outbound domains from Optimizely-served code, especially on checkout and wallet pages.
How to Mitigate: Remove any injected code and unknown collaborators from your Optimizely projects. Restrict which pages may load the snippet, especially payment pages, and enforce a CSP or SRI-style script monitoring. Assess the exposure of card data entered during the window with your payment processor and start PCI incident handling where applicable.
Evidence: BleepingComputer: Optimizely confirms signup-flow flaw used to inject malicious JS into customer projects · BleepingComputer: Optimizely hack infected CNN, Fox News, BBC, Salesforce sites · The Hacker News: hijacked Optimizely scripts served card skimmer and iOS exploit kit to 178+ organizations' sites
Read on the web · Every past edition
The Exploit Bulletin is free and daily. It publishes only what security teams must act on today — nothing else. Forward it freely.
Spot an error, or an exploit we missed? Reply here or email [email protected].