Fixed in 22.8R2.6 or the latest 25.1 release; the October fixes do not cover them. Patch urgently, then investigate for compromise. Rapid7
Trending breakdowns
The ones to act on, explained in plain English.
Critical/CVE-2026-114938
Java4Shell: a Base64 decoder flaw in OpenJDK that can allow remote code execution
What it is
A memory-corruption flaw in OpenJDK's hardware-accelerated Base64 decoder. Specially crafted Base64 input can corrupt heap memory and, under certain conditions, let an unauthenticated attacker run code remotely. Microsoft's page does not say whether it is being exploited in the wild.
Who's exposed
OpenJDK-based runtimes from 17.0.6 onwards, including Java 21, 25 and 27, on x86-64 processors with AVX-512 VBMI. ARM64 and other x86-64 CPUs are not known to be affected. Risk is highest where attacker-controlled input reaches the decoder.
What to do
Inventory every Java runtime, including those bundled in applications, appliances and containers. Update to the patched build from your Java vendor (see Oracle's November 2026 Critical Patch Update), internet-facing services first, then restart. Azure WAF rules give interim cover only.
Outlook leaks your NTLMv2 hash when a crafted message file is opened
What it is
A spoofing flaw in Outlook. Opening a specially crafted message file makes Outlook send the user's NTLMv2 authentication hash to an attacker. It was exploited before Microsoft shipped the fix.
Who's exposed
Anyone running an unpatched Outlook who can be persuaded to open a message file. The stolen hash can be cracked offline or relayed to impersonate the user.
What to do
Install the November Office / Microsoft 365 Apps update. Block outbound SMB (TCP 445) at the perimeter and restrict NTLM where you can, so a leaked hash has nowhere to go.
Critical unauthenticated remote code execution in Windows LDAP and Windows Search
What it is
Two of the critical fixes in a release covering 1,252 CVEs, 68 of them critical. Both allow remote code execution without logging in. The release also fixes Exchange and Active Directory issues.
Who's exposed
Domain controllers and any Windows host that exposes LDAP or Windows Search to the network. The CVE IDs are in the linked analysis.
What to do
Patch domain controllers first, then servers that expose Windows Search, then workstations. Where Windows Search isn't needed on a server, disable the service.
Security updates for Exchange Server Subscription Edition only. Exchange 2016 and 2019 get none. Microsoft's announcement does not list CVE IDs, so check the Security Update Guide, filtered to Exchange SE.
Who's exposed
Every Exchange server, including machines that only have the management tools installed. Exchange 2016 and 2019 should be treated as permanently vulnerable.
What to do
Install the November SU on every server, reboot and confirm the Exchange services started. Run the Health Checker to find servers that are behind, and re-run the Hybrid Configuration Wizard if you change the auth certificate.
Chrome use-after-free zero-day is exploited in the wild, and Edge is fixed too
What it is
A use-after-free flaw in Chrome's XML component, reported as exploited in the wild before the fix. It is the eighth Chrome zero-day of the year and is on CISA's Known Exploited Vulnerabilities catalogue.
Who's exposed
Chrome before 157.0.8103.50, and Microsoft Edge and other Chromium browsers until they take the same fix. Anyone who can be lured to a malicious page is at risk.
What to do
Update Chrome to 157.0.8103.50 or later and Edge to 157.0.4341.46 or later, then relaunch the browser. CISA's deadline for federal agencies is 24 November; treat that as your target too.
PHP2Shell: unauthenticated code execution in the PHP engine itself
What it is
Two memory-safety flaws in the PHP engine. Running out of memory part-way through a request leaves stale state behind, which a later request on the same worker can be steered into using. The result can be remote code execution. CVSS v4.0 9.2.
Who's exposed
Any PHP install, whatever the version, including appliances and services that bundle PHP. Internet-facing web servers come first.
What to do
Upgrade to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 and restart the workers. If you can't patch today, apply the PHP Foundation's temporary mitigations or take the system offline.