---
layout: post
title: "November 2026 security advisories: nginx2root, Java4Shell, Ruby2Shell, and a vCenter zero-day"
description: "Summarizes nginx2root (10 NGINX CVEs), OpenJDK Java4Shell (CVE-2026-114938), the PHP November 19 security releases (seven critical), Ruby2Shell (CVE-2026-132825), the exploited VMware vCenter authentication bypass (CVE-2026-123890), the Windows Narrator FastUnlock lock-screen bypass, and the Tails 7.17.1 incident, with an enterprise patch checklist."
author: Mark_Mew
categories: [Security]
tags: [CVE, NGINX, Apache HTTP Server, Java, OpenJDK, Ruby, Rails, Python, pip, LiteLLM, VMware, vCenter, Windows, Narrator, BitLocker, jQuery, ReDoS, Tails, uBlock Origin, PHP, CISA KEV]
keywords: [November 2026 vulnerabilities, nginx2root, NGINX HTTP/2 RCE, Java4Shell, CVE-2026-114938, PHP 8.5.13, CVE-2026-115560, PHPAfterShell, CVE-2026-126714, CVE-2026-129289, CVE-2026-119618, mod_http2, CVE-2026-133949, CVE-2026-40217, LiteLLM, CVE-2026-124749, pam-MySQL, Ruby2Shell, CVE-2026-132825, CVE-2026-123890, VMSA-2026-0009, FastUnlock, Windows Narrator, Tails 7.17.1, uBlock Origin XSS]
lang: en
date: 2026-11-20
last_modified_at: 2026-11-22
---

**Data current as of November 22, 2026 (Taiwan time).**

> **Update, Nov 22:** The PHP section now covers PHPAfterShell (CVE-2026-126714): PoC status, an exploit chain that does not need application gadgets, the limits of `session.upload_progress.enabled=0`, and fix status across platforms. Also added an "Other notable items" section covering the Apache HTTP Server mod_http2 RCE (CVE-2026-119618), pip's bundled eMudhra certificates (CVE-2026-133949), and the exploited LiteLLM sandbox escape (CVE-2026-40217), plus the pam-MySQL authentication bypass (CVE-2026-124749). CISA formally added vCenter CVE-2026-123890 to KEV on Nov 20 (deadline Nov 23); the earlier "single source" note has been corrected, and the flaw is now flagged as this month's top priority at the start of the article.

> **Update, Nov 21:** Added three sections: the Ruby security releases (Ruby2Shell and six other flaws), VMware VMSA-2026-0009 (an exploited vCenter authentication bypass), and the Windows Narrator FastUnlock lock-screen bypass (no CVE or fix yet). The timeline, patch priorities, and checklist are updated to match. Also added NGINX follow-up developments (distribution fix status and a container escape chained with a Linux kernel flaw), and rewrote the PHP section for the November 19 security releases (CVE-2026-115560 is now formally fixed). The original description of Censys's reproduction result was wrong and has been corrected.

> **Top priority this month: VMware vCenter CVE-2026-123890.** CVSS 3.1 9.8, no authentication required, exploited for about two months before the fix, and added to CISA KEV on Nov 20 with a federal deadline of Nov 23. Besides upgrading, check for compromise; see the "VMware: VMSA-2026-0009" section.

> Intended audience: operations and security staff. This article includes only items backed by original or credible secondary sources. The jQuery ReDoS issue has no CVE identifier and is covered in its own section below.

November's main items are three. Several memory-safety bugs in NGINX's HTTP/2 and HTTP/3 code were fixed on November 18 (known in the community as nginx2root). An OpenJDK Base64 decoder bug shipped in Oracle's November Critical Patch Update (known as Java4Shell). And Tails made an emergency removal of uBlock Origin on November 17 over a one-click XSS. Four more items arrived after November 18. PHP shipped security releases on November 19 fixing 17 advisories, seven of them critical. Ruby fixed seven memory-safety flaws, one of which (Ruby2Shell) is reportedly reachable without authentication in default Rails apps. Broadcom fixed the vCenter authentication bypass CVE-2026-123890, which Mandiant says has been exploited since September. And a zero-day called FastUnlock uses the Windows 11 Narrator to get past the lock screen; it has no CVE or fix yet.

## Timeline

| Date | Organization or product | Event | Identifier or advisory | Operational concern | Source |
|---|---|---|---|---|---|
| 11/9 | CISA | Four new KEV entries | GPUStack, SignalWire FreeSWITCH, OpenSSH, IBM Aspera Faspex | U.S. federal agency remediation deadline Nov 12 | [eSecurityPlanet](https://www.esecurityplanet.com/vulnerabilities/news-cisa-kev-gpustack-freeswitch-openssh-ibm-november-2026/) |
| 11/10 | CISA | Six new KEV entries | Barracuda ESG and others (see below) | Barracuda authentication bypass, CVSS v4.0 9.3 | [CISA advisory](https://content.govdelivery.com/accounts/USDHSCISA/bulletins/4325e4d) |
| 11/11 | Apache HTTP Server | 2.4.71 fixes 3 CVEs | CVE-2026-119618 | mod_http2 heap corruption and RCE; rated critical by Apache | [Apache httpd](https://httpd.apache.org/security/vulnerabilities_24.html) |
| 11/16–17 | Oracle | November Critical Patch Update includes OpenJDK | CVE-2026-114938 (Java4Shell) | Heap overflow under specific CPU and application conditions | [THN](https://thehackernews.com/2026/11/oracle-to-patch-11-java-flaws-today-as.html) |
| 11/17 | Tails | 7.17.1 emergency update removes uBlock Origin | No CVE seen (GHSA-cmqw-9r2w-6wv2) | One-click universal XSS | [Linuxiac](https://linuxiac.com/?p=223307) |
| 11/18 | F5 / NGINX | Security releases 1.30.7 and 1.31.9; 10 CVEs | CVE-2026-123007 and others | HTTP/2 memory corruption; known as nginx2root | [NGINX security advisories](https://nginx.org/en/security_advisories.html) |
| 11/18 | CISA | LiteLLM and three others added to KEV | CVE-2026-40217 | LiteLLM proxy sandbox escape, exploited; due 12/2 | [CISA KEV](https://www.cisa.gov/known-exploited-vulnerabilities-catalog) |
| 11/18 | Ruby | Security releases 4.0.10, 3.4.13, and 3.3.14; seven flaws fixed | CVE-2026-132825 (Ruby2Shell, GHSA-34m4-m9fh-gqp5) and others | Heap overflow in string case conversion; possible RCE | [Ruby advisory](https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/) |
| 11/19 | PHP | Security releases 8.5.13, 8.4.28, 8.3.37, 8.2.36 (8.6.0 GA the same day) | CVE-2026-115560, CVE-2026-129289, and 15 more GHSAs | Seven critical (CVSS v4.0 9.2), including session deserialization RCE and PHP-FPM request smuggling | [PHP security advisories](https://github.com/php/php-src/security/advisories) |
| 11/19 | Broadcom / VMware | VMSA-2026-0009 (revised to 0009.1 on 11/20) | CVE-2026-123890 and four others | Unauthenticated vCenter bypass, CVSS 3.1 9.8; Mandiant says it was exploited | [Broadcom advisory](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495) |
| 11/19 | pam-MySQL | Disclosed on oss-security; upstream pushed a fix | CVE-2026-124749 | Accounts with NULL passwords can log in over SSH with any password; researcher's own score 9.8 | [oss-security](https://seclists.org/oss-sec/2026/q4/788) |
| 11/19 | Windows 11 Narrator | FastUnlock zero-day published (uncoordinated disclosure) | No CVE yet | Physical access required; reaches Settings from the lock screen via Narrator | [Cyber Security News](https://cybersecuritynews.com/windows-11-narrator-lock-screen-0-day/) |
| 11/20 | CISA | vCenter and three others added to KEV | CVE-2026-123890, Apache Roller, Cisco Expressway, SAP NetWeaver | vCenter deadline only 3 days (11/23); forensic triage required | [CISA alert](https://www.cisa.gov/news-events/alerts/2026/11/20/cisa-adds-four-known-exploited-vulnerabilities-catalog) |
| 11/20 | pip | CVE published (fixed release 26.2.2 already shipped on 10/20) | CVE-2026-133949 | Bundled certifi includes eMudhra certificates; CVSS 9.3 | [CVE Brief](https://cvebrief.com/cve/cve-2026-133949/) |

## Key CVEs

| CVE | Product / type | Score (varies by source) | Known exploitation | Fix status and priority |
|---|---|---|---|---|
| CVE-2026-123007 | NGINX HTTP/2 flow-control memory corruption, possible RCE | nginx.org: major; CVSS v4.0 9.2 cited by F5 via Wiz and Tenable; CERT-EU: 8.1 | No ITW exploitation seen; a constrained public PoC exists | Upgrade to 1.30.7 / 1.31.9; **highest** |
| CVE-2026-123633 | NGINX HTTP/2 use-after-free | nginx.org: medium; CVSS v4.0 9.2 (secondary) | No ITW exploitation seen | Same; **highest** |
| CVE-2026-121810 | NGINX HTTP/3 use-after-free | nginx.org: medium | No ITW exploitation seen | Same; disable the QUIC listener as an interim step if QUIC is not needed |
| CVE-2026-123634 | NGINX resolver use-after-free | nginx.org: medium | No ITW exploitation seen | Same; high |
| CVE-2026-113425 | NGINX mail proxy use-after-free | nginx.org: major | No ITW exploitation seen | Same; sites without the mail module can deprioritize |
| CVE-2026-118899 | NGINX infinite loop reading client body over TLS 1.3 | nginx.org: major; secondary CVSS v4.0 8.7 | No ITW exploitation seen | Same |
| CVE-2026-114938 | OpenJDK Base64 decoder heap overflow (Java4Shell) | CVSS v3.1 8.1 (OpenJDK); CVSS v4.0 9.2 (Calif) | Not on KEV; attack attempts reported, success not confirmed | Upgrade to Oracle's November CPU or your vendor's build; high |
| CVE-2026-115560 | PHP session serializer mismatch leading to deserialization RCE (informational notice first issued 10/23) | CVSS v4.0 9.2 (PHP GHSA) | No ITW exploitation seen; the GHSA says command execution was demonstrated with Guzzle and Monolog gadgets | Upgrade to 8.5.13 / 8.4.28 / 8.3.37 / 8.2.36 and keep `session.upload_progress.enabled=0`; **highest** |
| CVE-2026-129289 | PHP-FPM request smuggling (when the front end reuses FastCGI connections) | CVSS v4.0 9.2 (PHP GHSA) | No ITW exploitation seen | Same; turn off FastCGI connection reuse until patched; **highest** |
| CVE-2026-129481 | PHP session use-after-free; incomplete fix for October's CVE-2026-109619 (PHP2Shell) | CVSS v4.0 9.2 (PHP GHSA) | No ITW exploitation seen; the GHSA says RCE has not been demonstrated | Upgrade (8.3 and later affected); **high** |
| CVE-2026-40217 | LiteLLM proxy `/guardrails/test_custom_code` sandbox escape | CVSS 9.5 (CVE Brief) | **CISA KEV (11/18)**; public PoC | Upgrade to 1.83.10 or later; **highest** |
| CVE-2026-119618 | Apache HTTP Server mod_http2 heap corruption and RCE | Rated critical by Apache; no CVSS | No ITW exploitation or public exploit seen | Upgrade to 2.4.71 or disable HTTP/2; **highest** (if HTTP/2 is enabled) |
| CVE-2026-124749 | pam-MySQL inverts `PAM_DISALLOW_NULL_AUTHTOK`; accounts with NULL passwords log in without a password check | CVSS 3.1 9.8 (researcher's own score; 8.1 also defensible) | No ITW exploitation seen | Fixed in Debian; no Ubuntu or upstream release yet; purge NULL/empty-string password rows first; **high** |
| CVE-2026-133949 | pip's bundled certifi includes eMudhra certificates | CVSS 9.3 (CVE record) | No ITW exploitation seen | Upgrade to pip 26.2.2 or later; medium (upgrading resolves it) |
| CVE-2026-132825 | One-byte heap overflow in Ruby string case conversion (Ruby2Shell), affecting single-byte encodings such as ISO-8859-x and Windows-125x | The Ruby and AWS pages reviewed give no CVSS number; Aikido rates it critical | No ITW exploitation seen; Ruby says known PoCs achieve RCE in some scenarios | Upgrade to 4.0.10 / 3.4.13 / 3.3.14; **highest** |
| CVE-2026-123890 | VMware vCenter (VMware Directory Service) authentication bypass | CVSS 3.1 9.8 (Broadcom) | **CISA KEV (11/20, due 11/23)**; Mandiant says exploited since September 2026; Broadcom's advisory does not mention it | Upgrade to 8.0 U3m, 9.0.2.0200, 9.1.1.0200, or VCF 5.2.5; **highest** |
| CVE-2026-123891 | VMware SDDC Manager authenticated SQL injection | CVSS 3.1 8.1 (Broadcom) | No ITW exploitation seen | Per VMSA-2026-0009; high |
| None (FastUnlock) | Windows 11 Narrator lock-screen bypass; code runs as WsiAccount | None | No ITW exploitation seen; public demo exists | No fix yet; BitLocker startup PIN, disable AutoPlay; medium (high where lost-device risk is high) |
| CVE-2026-116606 | Pre-authentication authorization bypass in Barracuda Email Security Gateway (requires the admin UI to be reachable); a crafted backup can be imported to rewrite global settings; chained with CVE-2026-111560 to gain root | CVSS v4.0 9.3 (most sources); Action1 lists 9.8 | CISA KEV (Nov 10); sources differ on exploitation details | Upgrade firmware to 9.4.0.030 or later; **highest** |
| CVE-2026-114819 | Oracle Text component of Oracle Database Server; a low-privileged attacker with Create Session can compromise Oracle Text over Oracle Net (may affect other products) | CVSS 3.1 9.9 (Oracle official matrix) | Not marked by Oracle | Upgrade affected branches (19.3–19.32, 21.3–21.24, 23.4.0–23.26.3); **highest** |
| CVE-2026-114848 | Oracle Text component of Oracle Database Server; same conditions as above | CVSS 3.1 9.9 (Oracle official matrix) | Not marked by Oracle | Upgrade affected branches (19.3–19.33, 21.3–21.24, 23.4.0–23.26.3); **highest** |
| CVE-2026-114822 | RDBMS component of Oracle Database Server; same conditions as above | CVSS 3.1 9.9 (Oracle official matrix) | Not marked by Oracle | Upgrade affected branches (23.4.0–23.26.4); **highest** |
| CVE-2026-114862 | PeopleSoft Enterprise PeopleTools (WebLogic component); unauthenticated attacker via HTTP can create, modify, or access critical data | CVSS 3.1 9.1 (Oracle official matrix) | Not marked by Oracle | Upgrade 8.61–8.63 per Oracle's patch; **high** |
| CVE-2026-91456 | WebLogic Server (Core); unauthenticated attacker via SOAP can take over the server | CVSS 3.1 9.8 (Oracle official matrix) | Not marked by Oracle | Upgrade affected branches (12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, 15.1.1.0.0); **highest** |
| CVE-2026-91469 | WebLogic Server (Core); unauthenticated attacker via HTTP can modify data and disrupt service | CVSS 3.1 9.4 (Oracle official matrix) | Not marked by Oracle | Same branches; **high** |
| CVE-2026-91470 | WebLogic Server (Core); unauthenticated attacker via T3 or IIOP can take over the server | CVSS 3.1 9.8 (Oracle official matrix) | Not marked by Oracle | Same branches; **highest** |
| CVE-2026-91500 | Access Manager (Authentication Engine); unauthenticated attacker via HTTP gains full data access and may affect other products (scope change) | CVSS 3.1 10.0 (Oracle official matrix) | Not marked by Oracle | Upgrade 12.2.1.4.0, 14.1.2.1.0; **highest** |
| CVE-2026-91507 | Access Manager (Authentication Engine); unauthenticated attacker via HTTP can modify data and read a subset (scope change) | CVSS 3.1 9.3 (Oracle official matrix) | Not marked by Oracle | Same branches; **high** |
| CVE-2026-91510 | Access Manager (Authentication Engine); unauthenticated attacker via HTTP gains full data access and causes partial DoS | CVSS 3.1 10.0 (Oracle official matrix) | Not marked by Oracle | Same branches; **highest** |
| CVE-2026-91561 | Service Bus (Core); low-privileged attacker via RMI can affect Service Bus data (scope change) | CVSS 3.1 9.6 (Oracle official matrix) | Not marked by Oracle | Upgrade 12.2.1.4.0, 14.1.2.0.0; **high** |
| CVE-2026-91569 | WebLogic Server (TopLink Integration); unauthenticated attacker via HTTP can take over the server | CVSS 3.1 10.0 (Oracle official matrix) | Not marked by Oracle | Upgrade 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0, 15.1.1.0.0; **highest** |
| CVE-2026-91570 | WebLogic Server (TopLink Integration); unauthenticated attacker via HTTP can take over the server | CVSS 3.1 9.8 (Oracle official matrix) | Not marked by Oracle | Same branches as CVE-2026-91569; **highest** |
| CVE-2026-91583 | WebLogic Server (TopLink Integration); unauthenticated attacker via HTTP can take over the server | CVSS 3.1 9.8 (Oracle official matrix) | Not marked by Oracle | Same branches as CVE-2026-91569; **highest** |
| Other November CSPU CVSS 10.0 items (WebLogic Server, Access Manager, Business Intelligence, and others) | Secondary sources list conflicting CVE identifiers; not verified in this article | CVSS v3.1 10.0 | Not verified | Verify against Oracle's risk matrices and patch each item; **highest** |

Scores are listed only where each source states them. **CVSS v3.1 and v4.0 scores should not be compared directly.** The 9.2 and 8.1 figures for NGINX come from different sources and versions and should not be mixed.

## NGINX: the 10 CVEs in nginx2root

NGINX released stable 1.30.7 and mainline 1.31.9 on November 18. Per the affected ranges listed on nginx.org, **mainline builds up to and including 1.31.8 and stable builds up to 1.30.6 need attention** for the 10 CVEs. CERT-EU also lists 1.30.x as affected and notes the NGINX Plus version ranges. nginx.org gives severity words only, not CVSS numbers.

- **CVE-2026-123007**: integer underflow and memory corruption in HTTP/2 flow control, affecting builds back to 1.9.5. It only applies when HTTP/2 is enabled. A Rapid7 researcher published a PoC. Tenable considers it constrained: x86-64 with glibc, roughly 128 GB of HTTP/2 traffic, ASLR must be defeated, and code runs only as the NGINX worker. Censys reproduced the flow-control accounting error with a compact cleartext HTTP/2 (h2c) test of about 5.69 MB, but it caused no crash and no RCE; Rapid7's crash and RCE stages still require large traffic volumes.
- **CVE-2026-123633**: HTTP/2 use-after-free. Wiz notes it can be triggered on reverse proxies when connection slots run low.
- **CVE-2026-121810**: HTTP/3 use-after-free. Requires a QUIC / HTTP/3 listener.
- **CVE-2026-123634**: use-after-free in resolver response handling. Tenable notes that turning off `mirror` is not enough; use a fixed `proxy_pass` upstream.
- **CVE-2026-113425**: use-after-free in the mail proxy module. Tenable recommends binding mail listeners to loopback or blocking them with a firewall.
- **CVE-2026-118899, CVE-2026-120993, CVE-2026-125283, CVE-2026-120967, CVE-2026-123640**: the remaining five, ranging from lower to higher severity depending on nginx.org and secondary sources.

**Exploitation status:** As of Nov 19, Tenable and CERT-EU report no observed exploitation, and CISA has not added these to KEV. CERT-EU notes that researchers have demonstrated exploitation of CVE-2026-123007.

**Interim mitigations:** `http2 off;` (or removing `http2` from `listen`) only blocks CVE-2026-123007 and CVE-2026-123633. Turning off the QUIC listener only blocks CVE-2026-121810. These are stopgaps and do not replace upgrading.

**Upgrade note:** Xint notes that a **restart** is needed after upgrading, not just a reload, because reload does not replace the running binary. Tenable also reports that NGINX Plus releases R34 to R36 are unpatched and must move to the 37.x branch; SecurityWeek and Censys list the Plus fix versions as 37.0.8.1 and 37.3.0.1. The Plus fix versions come from secondary sources, so check them against F5's advisory before upgrading.

### Follow-up, Nov 19–21

- **No new release:** As of Nov 21, the latest on nginx.org is still the Nov 18 1.30.7 / 1.31.9, and the advisories page shows no revisions.
- **Exploitation status:** GetPageSpeed (updated Nov 20) and SecurityWeek (Nov 19) both report no observed exploitation and no CISA KEV listing. The only public exploit PoC is Rapid7's, for CVE-2026-123007. What Censys published on GitHub is test traffic for detection and patch verification, not an exploit. Wiz says it will not release its exploits.
- **Chaining with a Linux kernel flaw can escape containers:** Xint says it chained CVE-2026-123007 with a separate flaw in the Linux kernel's SCTP subsystem and, in testing, escaped a Docker container running NGINX and gained root on the host. According to GetPageSpeed and Censys, that kernel flaw (a use-after-free in the SCTP send path, present since Linux 4.15) **has no CVE and no fix yet**, and Censys says it has not verified the chain. GetPageSpeed suggests adding `install sctp /bin/false` under `/etc/modprobe.d/` to stop the SCTP module from autoloading (it does not unload a module that is already loaded). This also means "NGINX runs in a container" is not a reason to lower the priority.
- **Distribution fix status:** Distributions mostly fix by backporting, so **package versions will be lower than 1.30.7, and `nginx -v` alone cannot tell you whether you are fixed.** Go by each distribution's advisory.

| Distribution | Status (as of Nov 20) | Source |
|---|---|---|
| Debian | Fixed in bookworm 1.22.1-9+deb12u11 (DLA-4918-1) and trixie 1.26.3-3+deb13u11 (DSA-6642-1); forky not yet | [Debian tracker](https://security-tracker.debian.org/tracker/CVE-2026-123007) |
| Ubuntu | USN-9159-1 (Nov 19): 24.04 1.24.0-2ubuntu7.20, 22.04 1.18.0-6ubuntu14.23, and others; 20.04 and older need Ubuntu Pro | [Ubuntu](https://ubuntu.com/security/CVE-2026-123007) |
| Amazon Linux | AL2023 1.30.7-1.amzn2023.0.1; AL2 nginx1 1.30.7-1.amzn2.0.1 | GetPageSpeed |
| Alpine | 1.28.3-r8 on 3.22 / 3.23; 1.30.7-r0 on 3.24 and edge | GetPageSpeed |
| AlmaLinux 9 / 10 | Backported (ALSA-2026:A024 / A025); the first Nov 18 builds fixed only the two HTTP/2 flaws | GetPageSpeed |
| RHEL 8 / 9 / 10, Rocky Linux | No fix yet (Red Hat lists them as affected) | GetPageSpeed; not checked directly with Red Hat |
| CentOS 7 | No fix (EOL) | GetPageSpeed |

- **Products that embed NGINX:** According to GetPageSpeed, Plesk (18.0.82 Update 4, 18.0.81 Update 9) and cPanel EasyApache 4 (build 25.98) shipped fixes on Nov 19. OpenResty, Angie, Tengine, and freenginx had no fixed release as of Nov 20. Kubernetes ingress-nginx was archived in March 2026 and will not get a fix; the only options are turning off HTTP/2 or moving to another ingress controller. Sophos says its hosted Taegis XDR / VDR are fixed and many of its products are not affected, and it is still investigating others.

## Java4Shell: an OpenJDK flaw in Oracle's November CPU

CVE-2026-114938 sits in HotSpot's x86 Base64 decode intrinsic (the AVX-512 path), used by the basic and URL decoders in `java.util.Base64`. The MIME decoder is not affected. According to Equixly's technical write-up:

- **Conditions:** x86-64 with AVX-512 VBMI and AVX-512 BW (for example, Intel Ice Lake or later, or AMD Zen 4 or later). ARM (Graviton, Ampere, Apple Silicon) is not affected.
- **Trigger:** untrusted Base64 data whose length is 1 to 3 characters more than a multiple of 64 and ends with `=`, and which reaches `java.util.Base64`.
- **Result:** a write of 62 or 63 bytes past the output array on the Java heap. The attacker cannot choose the bytes written directly, but heap grooming can influence placement.

**Attack surface and scores:** Oracle states that exploitation requires an application to pass untrusted data to the affected Java APIs. Calif's public PoC only triggers the overflow; its RCE chain is not public. The CVSS v4.0 9.2 score comes from Calif, and the CVSS v3.1 8.1 score comes from OpenJDK. **"RCE" is currently the researchers' assessment and should not be presented as a publicly available full exploit.**

**Exploitation status:** GreyNoise reported attack attempts around Nov 18 but has not confirmed successful exploitation. Equixly reports no observed exploitation. Not on CISA KEV.

**Fixed versions:** Oracle lists 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1, and the Java 8 Performance Pack build 8u513-perf. GraalVM and other distributions use their own version numbers; confirm with your vendor. Standard Java 8 and 11 are not listed as affected.

**Interim mitigation:** Calif suggests `-XX:-UseBASE64Intrinsics`. Oracle and OpenJDK have not confirmed this, though projects such as Keycloak have adopted it. Note that `-XX:UseAVX=2` fails to start on ARM and should not be applied to ARM hosts.

**Oracle page not verified:** An attempt to read Oracle's November CPU page returned 403 Forbidden. Whether CVE-2026-114938 appears on that page, its official score, and its version table are therefore based on secondary sources such as Equixly and Tenable. **Check Oracle's official advisory before upgrading.**

## Tails 7.17.1: removing uBlock Origin

On **November 17**, Tails released 7.17.1 as an emergency update, removing uBlock Origin from its bundled Tor Browser. The reason is a one-click universal XSS: a malicious site can hijack uBlock's element picker, plant a trusted filter, and then run the attacker's JavaScript on other sites the user visits. Tails says it is not aware of any real-world attacks.

- **Affected security levels:** Standard and Safer are affected; Safest is not (as reported by Linuxiac, citing Tails).
- **Known remediation:** Restarting Tails clears any malicious uBlock Origin configuration that may have been planted. The extension is expected to return once the issue is fixed.
- **Other changes:** Linux kernel updated to 6.12.117, plus several firmware packages.
- **Upgrading:** Automatic upgrades work from 7.0 onward and keep Persistent Storage. A fresh install erases Persistent Storage, so back it up first.
- **CVE:** No CVE is mentioned. The GHSA identifier GHSA-cmqw-9r2w-6wv2 could not be opened, so **the fixed uBlock Origin version and its public date are unverified.** A single secondary source says upstream shipped 1.75.4 on Nov 3; check the official uBlock Origin advisory.

**General user advice:** Until patched, avoid visiting untrusted sites, and do not use the element picker on untrusted pages.

## Ruby: Ruby2Shell and six other flaws

On **November 18**, Ruby released 4.0.10, 3.4.13, and 3.3.14, fixing seven memory-safety flaws in the regular-expression engine and in string case conversion.

| Branch | Affected versions | Fixed version |
|---|---|---|
| 4.0 | 4.0.0–4.0.9 | 4.0.10 |
| 3.4 | 3.4.0–3.4.12 | 3.4.13 |
| 3.3 (security maintenance) | 3.3.13 and earlier | 3.3.14 |
| 3.2 and earlier | End of life | **No fix**; move to a supported branch |

**About the CVE identifier:** Ruby's advisory says CVEs have been requested but not yet assigned, so it uses GHSA identifiers only. The identifier CVE-2026-132825 comes from AWS and Aikido, both of which map it to GHSA-34m4-m9fh-gqp5. The other six have no CVE yet. As with jQuery, **scanners that inventory only by CVE may miss them.**

**Ruby2Shell (GHSA-34m4-m9fh-gqp5):** a one-byte heap overflow during string case conversion. According to Aikido, only strings in legacy single-byte encodings such as ISO-8859-x or Windows-125x are affected; UTF-8 is not. It is triggered by calling methods such as `upcase`, `capitalize`, or `swapcase` on attacker-controlled strings. AWS and Aikido both say Rails and classic-style Sinatra can reach this code in their **default request handling**, so it may be triggerable over the network without authentication. Ruby says known PoCs achieve RCE in some scenarios, but exploitability varies widely by application and runtime environment.

**The other six** (all from Ruby's advisory, no CVEs yet):

- GHSA-7x2q-68qv-6p8x: double free in regular-expression compilation; possible RCE.
- GHSA-87fm-7w84-j2px: integer overflow in case conversion leading to a heap overflow; possible RCE.
- GHSA-wpqw-5qxg-m68r: out-of-bounds read in case-insensitive matching; possible RCE.
- GHSA-3p8q-wmhx-vm2w: integer overflow in regular-expression compilation leading to a heap overflow; possible RCE.
- GHSA-7whj-cfh7-xgm4: heap overflow in `Regexp#to_s`; possible information disclosure or RCE.
- GHSA-pvgc-g7gj-pv6h: out-of-bounds read in case-insensitive backreference matching; may leak memory or crash the process.

The flaws tied to regular-expression compilation require the application to **compile attacker-controlled patterns**. Most applications face lower risk, but services that offer search syntax, rule engines, or user-defined regexes should prioritize them.

**Exploitation status:** As of Nov 19, Aikido reports no attacks seen; the researchers plan to publish a PoC in about a week. None of the pages reviewed mention CISA KEV. On scoring, the Ruby, AWS, and Aikido pages reviewed give no CVSS number, so this article lists none.

**Interim mitigations:** Ruby offers no workaround. AWS recommends restricting internet-facing Ruby applications until upgraded, and avoiding processing untrusted input in non-UTF-8 encodings where possible. Version 1.29 of the AWS WAF Known Bad Inputs managed rule group adds three Ruby2Shell rules (Count mode by default; they may match legitimate traffic, so review before switching to Block).

**Downstream products:**

- **AWS:** Elastic Beanstalk's Amazon Linux 2023 Ruby platforms were updated to 4.15.4 on Nov 19. Lambda's managed Ruby runtimes are being updated; container image users must rebuild on the latest base images. The Amazon Linux 2 core ruby package is not affected.
- **Self-hosted products that bundle Ruby:** Aikido notes that as of Nov 19, the latest releases of GitLab 19.6.0, GitHub Enterprise Server 3.22.5, Mastodon 4.7.5, OpenProject 17.9.7, Discourse 2026.10.1, and Chatwoot 4.20.0 still bundle an affected Ruby. These need new vendor releases; until then, Aikido suggests restricting access with a VPN or IP allowlist.
- **After upgrading,** restart application servers such as Puma, Unicorn, and Passenger, and rebuild the Ruby in container images and CI.

## VMware: VMSA-2026-0009 and the exploited vCenter authentication bypass

Broadcom published VMSA-2026-0009 on **November 19**, fixing five vulnerabilities, and revised it to VMSA-2026-0009.1 on **November 20** to clarify the affected VMware Tools versions. Broadcom rates it Critical and lists **no workaround**.

| CVE | Component | Type | CVSS 3.1 (Broadcom) |
|---|---|---|---|
| CVE-2026-123890 | vCenter (VMware Directory Service) | Authentication bypass | 9.8 |
| CVE-2026-123891 | SDDC Manager | Authenticated SQL injection | 8.1 |
| CVE-2026-123892 | SDDC Manager | Authenticated command injection (high privileges required) | 7.2 |
| CVE-2026-123893 | SDDC Manager | Local privilege escalation to root (admin required) | 6.7 |
| CVE-2026-123894 | VMware Tools for Windows | SAML token signature bypass (requires a guest alias mapping and a local privileged process in the guest) | 6.7 |

**Fixed versions** (Broadcom response matrix):

- **vCenter:** 8.0 → 8.0 U3m; VCF / vSphere Foundation 9.0.x → 9.0.2.0200; 9.1.x → 9.1.1.0200; VCF 5.x → 5.2.5 (async patching per KB 88287).
- **vCenter 7.0:** general support ended on 2025-10-02; only customers with extended support contracts can contact Broadcom. **Treat 6.5 and 6.7 as affected.**
- **SDDC Manager:** 9.1.x → 9.1.1.0200; 9.0.x → 9.0.2.0100; 5.x → 5.2.5.
- **VMware Tools for Windows:** 13.x → 13.1.5.0; 12.3.x–12.5.x → 12.5.5 (12.4.10 for 32-bit Windows). Broadcom's Q&A and Rapid7 also mention 11.x as affected, which does not fully match the response matrix.
- **Not affected:** ESX, NSX, VCF Operations, VCF Automation, Workstation, Fusion.
- Telco Cloud Platform and Telco Cloud Infrastructure follow KB463116.

**Systems with the July fix still need this update:** Broadcom's Q&A states that CVE-2026-123890 is a new and distinct issue, and the July fix for CVE-2026-59309 does not protect against it.

**Exploitation status:** Broadcom's advisory and Q&A do **not** mention exploitation. According to Help Net Security, Rapid7, and others relaying Google/Mandiant's report, the suspected China-nexus group ARMORY CASTLE (formerly UNC5221) has exploited the flaw since at least early September 2026. Its initial access came through a BeyondTrust Remote Support zero-day (CVE-2026-102764). After compromise it created new SSO administrator accounts, copied the vmdir database, forged SAML tokens (Golden SAML), and moved on to ESXi. This article did not check these details against Google's original report. **CISA added CVE-2026-123890 to KEV on Nov 20, gave federal agencies only 3 days to patch (Nov 23), and flagged it as requiring forensic triage**; both the CISA alert and the KEV catalog confirm this. Added in the same batch were one flaw each in Apache Roller, Cisco Expressway, and SAP NetWeaver.

**Upgrade notes (Broadcom Q&A):**

- vCenter updates are **not eligible for vCenter Quick Patch**. Running VMs are unaffected during the update, but management interfaces go down briefly, and Standard Key Provider operations such as new encryption and key rotation are unavailable meanwhile.
- Fixes are cumulative; earlier patches such as VMSA-2026-0008 are not prerequisites.
- Applying 8.0 U3m or 9.0.2.0200 **blocks upgrades to VCF 9.1.1** (a back-in-time restriction). Broadcom advises those planning to move to 9.1 to wait briefly for 9.1.2.
- Disabling guest operations, or stopping or uninstalling VMware Tools, are **not** mitigations for CVE-2026-123894. Check alias mappings in the guest with `VGAuthCLI.exe list`.

**Compensating controls (not an official workaround):** Until patched, restrict the vCenter management interface to admin workstations or a jump host. A third-party article (dev.to) recommends allowing TCP 2012 only from management hosts and alerting on scans of 443, 2012, 5480, and 9080. This is an individual author's suggestion; Broadcom and the other sources do not mention it.

**Compromise assessment:** Because exploitation preceded the fix by about two months, **upgrading alone is not enough.** Check for unknown SSO administrator accounts (including unusual sign-ins to administrator@vsphere.local), SSH unexpectedly enabled on the VCSA, and sessions from unfamiliar addresses, and confirm logs are shipped to a SIEM outside vCenter. If Golden SAML abuse is suspected, rotate the SSO signing certificates.

## Windows Narrator: FastUnlock lock-screen bypass (no CVE yet)

On **November 19**, a researcher (most reports call them Nightmare Eclipse, GitHub account MSNightmare; spellings vary across sources) published a Windows 11 zero-day called FastUnlock on GitHub, **without coordinating with Microsoft.** ThreatLocker has reproduced part of the result.

**How the attack works (per HWBusters):**

1. The attacker needs **physical access** to a powered-on computer sitting at the lock screen, with at least one local account linked to a Microsoft account.
2. On the account-recovery screen, pressing `Win+U` starts Narrator, and focus lands on a window that should not be reachable before sign-in.
3. Using Caps Lock, the arrow keys, and Enter, the attacker reaches Narrator settings, then goes to Bluetooth & devices → AutoPlay.
4. A plugged-in USB drive opens in File Explorer, and code runs as **WsiAccount** (not the signed-in user, and not SYSTEM or an administrator).

**Tested environment:** Windows 11 26H2 with the November 2026 security updates. Windows 10 was not tested.

**What it bypasses:** Cyber Security News, HWBusters, and GBHackers all state that this is **a lock-screen bypass, not a break of BitLocker encryption**, and it cannot decrypt a powered-off drive. The risk is that TPM-only BitLocker unlocks automatically at boot, leaving the lock screen as the only barrier. Sources disagree on what WsiAccount can read or write and whether administrator rights are reachable (HWBusters cites Tom's Hardware saying an administrator account can be created under certain conditions; other sources say the public demo does not prove this). The researcher's public video also does not show the final USB execution step.

**Microsoft's response:** As of Nov 20, **there is no advisory, CVE, or fix.** Cyber Security News notes that the November BitLocker CVEs (CVE-2026-97015 and CVE-2026-119832) are unrelated to FastUnlock and should not be mistaken for a fix. The next scheduled update is Dec 8. All sources report no exploitation in the wild.

**Not the July Narrator flaw:** CVE-2026-58635 (Windows Narrator Braille elevation of privilege) is a different issue fixed in the July 2026 Patch Tuesday and is unrelated to FastUnlock. The details of that CVE could not be read from the MSRC page during this research.

**Mitigations:**

- **Switch BitLocker to TPM + startup PIN** (a pre-boot PIN, separate from the Windows sign-in PIN), so an attacker without the PIN cannot reach an unlocked system. This is the main measure recommended by several sources.
- **Shut down or hibernate when leaving the device; do not just sleep it:** waking from sleep does not require the startup PIN.
- **Disable AutoPlay for removable media** to cut off the USB execution step.
- The researcher suggests blocking the Narrator executable with AppLocker or an ACL. This affects users who rely on the screen reader, so **do not apply it broadly**; use it only on high-risk endpoints with no accessibility needs.
- Manage physical access: prioritize laptops and unattended endpoints in meeting rooms and public areas.

## PHP: November 19 security releases fix 17 advisories

The PHP 10/21 security releases and the 10/26 KEV update have moved to the [October 2026 security advisories]({% link _posts/en/2026-10-23-october-critical-cve-security-incidents.md %}). The 10/23 informational notice (CVE-2026-115560) had no fix at the time; it is now formally fixed in the November 19 security releases.

On **November 19**, PHP released 8.5.13, 8.4.28, 8.3.37, and 8.2.36, and PHP 8.6.0 reached general availability the same day with the same fixes. The php.net announcements say only "This is a security release"; the details are in [php-src's GitHub Security Advisories](https://github.com/php/php-src/security/advisories): 17 GHSAs in total (seven critical), plus one dependency upgrade for uriparser (CVE-2026-48841), which is why some sources say 18 CVEs.

- **The 10/21 releases (8.5.12, 8.4.27, and so on) are still in the affected ranges**, so environments upgraded last month need to upgrade again.
- **8.1 and older:** PHP no longer provides updates. The GHSA for CVE-2026-129291 explicitly lists 8.1.20–8.1.34 as affected with no fix. **8.2 reaches end of life on 2026-12-31**, so plan that upgrade too.

**The seven critical issues (all CVSS v4.0 9.2, per each GHSA):**

| CVE | Component | Type | Affected branches | Notes |
|---|---|---|---|---|
| CVE-2026-115560 | session | Serializer mismatch leading to deserialization RCE | 8.2–8.5 | Formal fix for the 10/23 informational notice |
| CVE-2026-126714 | session (files handler) | Interrupted write mixes old and new data, which can lead to deserialization RCE | 8.2–8.5 | Known as PHPAfterShell, see below; other session storage backends are not affected by this item |
| CVE-2026-129481 | session | Use-after-free after an interrupted session shutdown | 8.3–8.5 | Incomplete fix for October's CVE-2026-109619; RCE not demonstrated |
| CVE-2026-129289 | PHP-FPM | Request smuggling via an unread request body | 8.2–8.5 | Requires the front end to reuse FastCGI connections |
| CVE-2026-129496 | ext/date | Timezone cache use-after-free | 8.2–8.5 | Can crash an FPM worker remotely; native code execution demonstrated locally |
| CVE-2026-129474 | engine | Use-after-free in `__call` / `__callStatic` backtrace arguments | 8.5 only | The GHSA says RCE is confirmed on 8.5 (known memory addresses needed) |
| CVE-2026-129182 | engine | Use-after-free from `last_fatal_error_backtrace` being repopulated after shutdown | 8.5 only | RCE not demonstrated |

**Other notable items:**

- **CVE-2026-129291** (High, CVSS v4.0 8.8): a use-after-free in PHP-FPM's epoll code that lets a local attacker in an unprivileged FPM worker run commands as the FPM master (usually root). It requires the epoll backend and a pool with `catch_workers_output` enabled. The default is off, but the GHSA notes that **the official PHP-FPM Docker images enable it**, and root command execution was reproduced on unmodified 8.5.12 images.
- **CVE-2026-128090** (High, CVSS v4.0 7.7): a PHAR OpenSSL signature can be downgraded to a keyless hash, affecting applications that rely on a `.pubkey` file to verify phars.
- Others include an XSS on the FPM status page, out-of-bounds read/write in CGI `PATH_INFO` handling, memory bugs in SOAP and DOM, and mixed-case HTTPS / FTPS URLs sending data in plaintext.

**Key conditions and interim mitigations** (per each GHSA):

- **CVE-2026-115560:** After the fix, upload progress is off by default, and runtime changes to session settings are rejected while it is on. The GHSA still advises that installs that do not need the feature keep `session.upload_progress.enabled=0` in **every** configuration that can write to the same session store (set before request input is read; `ini_set()` is too late). Installs that need the feature must use the same `session.serialize_handler` for all readers and writers. The `ini_set()` path described in the 10/23 notice is only one route; **exposure does not require a runtime change**, and sharing a session store across applications, pools, vhosts, or the CLI is in scope.
- **CVE-2026-129289:** The demonstrated attack applies only when the front end **keeps FastCGI connections open for reuse**, for example NGINX `fastcgi_keep_conn on`, Apache mod_proxy_fcgi `enablereuse=on`, or HAProxy FastCGI keep-alive, and the application opens `php://input` without reading it to the end. Standard configurations that close the FastCGI connection after each request are not affected. Turn off connection reuse until patched.
- **CVE-2026-129481:** Turning off upload progress **does not** cover this path. The GHSA's stopgap is `pm.max_requests=1` (at a high performance cost).
- **CVE-2026-129474:** The demonstrated remote attack needs `fatal_error_backtraces=1` and `zend.exception_ignore_args=0`; `php.ini-production` sets `zend.exception_ignore_args=1` by default. The stopgap for **CVE-2026-129182** is `fatal_error_backtraces=0` plus a restart.
- **CVE-2026-129291:** Turn off `catch_workers_output`.

### PHPAfterShell (CVE-2026-126714)

depthfirst named CVE-2026-126714 PHPAfterShell. The research began as a review of October's PHP2Shell fix, so **servers that applied the October fix are still affected**. The GHSA credits zplinn as the reporter, which differs from depthfirst's account; this article lists both.

**How it works (per the GHSA):** The default `files` session handler overwrites the file from the start with `pwrite()` and truncates only when the new data is shorter. If the worker is killed mid-write, the file becomes "the front of the new data plus the tail of the old data," and the next `session_start()` deserializes it as a valid session. The fixed releases truncate before writing.

**Exploitation conditions:**

- The default `files` handler is in use. Redis and database backends are not affected by this write defect; Memcached is not mentioned in the sources reviewed.
- The attacker can influence session contents. Upload progress is one route, but the GHSA says it is enough for the application to store large attacker-controlled strings in the session.
- The write is interrupted at a critical moment: depthfirst used memory pressure to trigger the OOM killer, and Wiz also mentions memory-limit or timeout settings. In threaded builds, a memory-limit failure in another thread can also end the process mid-write.
- **An application gadget chain is not necessarily required:** the GHSA says "a suitable object gadget chain in the application," but according to Cyber Kendra, Ostorlab, and others, depthfirst's exploit chain uses a memory-corruption bug in a built-in PHP class and does not depend on application code. So "our code has no dangerous gadgets" is not a reason to lower the priority.
- Even short of RCE, a spliced session can corrupt state such as identity, authorization, CSRF tokens, or shopping carts.

**`session.upload_progress.enabled=0` blocks only one route:** The GHSA, depthfirst, and Slovenia's SIGOV-CERT all say it removes only the easiest input route and does not fix applications that store attacker-controlled data in the session themselves. The setting must go in php.ini or the FPM pool; `ini_set()` and `.user.ini` are too late. After upgrading, explicitly setting it to `On` overrides the new default (off) and reopens this route. Other interim measures (per Ostorlab): limit the length of user strings written to the session, and switch to an atomic backend (a database, or Redis with transactions).

**PoC status (sources disagree):**

- What depthfirst published is a harmless demonstration that only proves the spliced session decodes to an attacker-chosen object; it does not execute code by itself. The final RCE step was not published (Cyber Kendra says it is shown only in a video).
- CSIRT Italia (Nov 20) and HKCERT say a PoC for CVE-2026-126714 is "available online," but neither links to it. Precursor Security says it could not confirm public exploit code.

**Exploitation status:** As of Nov 20, PHP, Wiz, Ostorlab, and Cloudflare all report no observed exploitation, and it is not on CISA KEV. FIRST's first EPSS score is 0.18 (97th percentile); CVE-2026-115560 from the same release scored 0.56. Several Japanese government agencies and companies took websites or forms offline as a precaution, but no compromises have been reported.

**Fix status by platform (as of Nov 20, mostly per Precursor Security's roundup):**

| Platform | Status |
|---|---|
| Docker official PHP images | Updated Nov 19 |
| Debian | Fixed in trixie (DSA-6641-1) and bookworm (DLA-4916-1); forky not yet |
| Ubuntu | Fixed in 22.04, 24.04, 26.04, 26.10, and ESM releases |
| Amazon Linux | AL2023 fixed (AWS 2026-190-AWS); AL2 not yet |
| SUSE | Some versions fixed; others still affected |
| RHEL 8/9/10 | **No fixed packages yet** (Red Hat's CVE-2026-115560 page) |
| Cloudflare WAF | Since Nov 20, blocks known attack patterns by default on all plans, including Free |

**Detection hints (per Ostorlab):** `PHP_SESSION_UPLOAD_PROGRESS` in access logs, `|O:` or `|C:` object records in session files, and "Failed to decode session" errors.

**Disputed affected range:** The GHSA lists 8.2–8.5 and, based on code inspection, says the issue has existed since PHP 4.1.0, but it does not list 8.1. Cycode says every release from 8.1 back is affected; depthfirst says the official EOL mitigation branches (7.4, 8.0, 8.1) are not affected and only older unpatched builds are. If you run 8.1 or older, the main remedy is moving to a supported branch.

### PHP overall exploitation status

**Exploitation status:** Apart from the CSIRT Italia and HKCERT PoC claims above, none of the sources reviewed report in-the-wild exploitation. PHP Architect says none of the seven critical issues is on CISA KEV (not checked directly here). October's PHP2Shell flaws (CVE-2026-109618, CVE-2026-109619) are on KEV, and this release's CVE-2026-129481 is an incomplete fix for 109619. This release's items have no exploitation record of their own, but attackers already target the same attack surface, so **prioritize them**.

**After upgrading,** restart PHP-FPM or Apache, and rebuild PHP in container images and CI as well.

## Other notable items: Apache HTTP Server, pip, LiteLLM and pam-MySQL

### Apache HTTP Server: mod_http2 RCE (CVE-2026-119618)

Apache released httpd 2.4.71 on **November 11**, fixing 3 CVEs. Apache rates CVE-2026-119618 **critical**: a synchronization flaw in mod_http2's `assign_headers()` can lead to heap corruption and RCE.

- **Affected versions**: httpd 2.4.55–2.4.70, and the standalone mod_h2 releases on GitHub from 2.0.8 through 2.0.42. The fixed version is 2.4.71.
- **Precondition**: HTTP/2 must be enabled (mod_http2 is off by default). Servers that only run HTTP/1.1 are not affected.
- **Score**: Apache gives only a severity word, no CVSS. BleepingComputer quotes Wiz rating it critical, but "no official score is available."
- **Finders**: reported separately by Anthropic's open-source code scanning and by Google Cloud Vulnerability Research.
- **Exploitation status**: Wiz says it is unaware of any public exploits or attacks.
- **Interim mitigation**: watchTowr recommends "patch now or drop h2 until you can," for example by limiting `Protocols` to `http/1.1`. The sources reviewed do not mention distribution fix status; go by your distribution's advisory. As with NGINX, backported package versions may be lower than 2.4.71.

### pip: bundled eMudhra certificates no longer trusted (CVE-2026-133949)

- **Issue**: the certifi certificate bundle shipped inside pip before 26.2.2 includes eMudhra CA certificates. The CVE record calls them "compromised," which may lead to improper certificate validation (CWE-295). CVE Brief says an attacker could use this to man-in-the-middle package downloads. The sources reviewed do not explain what "compromised" means exactly (key compromise, misissuance, or distrust).
- **Score**: CVSS 9.3 (CVE record; source listed as the pip maintainers; no vector shown).
- **Timing gap**: the CVE was published only on **November 20**, but the fixed release, pip 26.2.2, shipped on **October 20** (it updated the bundled certifi). Its changelog did not mark it as a security fix at the time. The latest release is 26.3 (November 2). **Environments already on 26.2.2 or later are not affected.**
- **System certificates do not necessarily protect you**: since pip 24.2, pip by default uses system certificates "in addition to certifi," which means certifi's bundled roots are still trusted. The sources reviewed do not say whether this mitigates the issue, and this article does not recommend relying on it.
- **What to watch for**: old venvs, container images, and CI environments often keep the old pip bundled when they were created; upgrade it explicitly. Whether the pip bundled with CPython's ensurepip needs an update was not checked this time.
- **Exploitation status**: no public exploit seen; not in CISA KEV. pip's GitHub Security Advisories page currently has no matching advisory.

### LiteLLM: exploited sandbox escape (CVE-2026-40217)

- **Issue**: the LiteLLM proxy's `/guardrails/test_custom_code` endpoint allows escaping the custom code sandbox through bytecode rewriting, leading to arbitrary code execution. KEV describes it as an "Unprotected Alternate Channel" (CWE-420).
- **Score**: CVSS 9.5 (CVE Brief; scorer not named).
- **Timing**: the CVE was published back in April 2026. CISA added it to KEV on **November 18**, with a federal remediation due date of **December 2**.
- **Authentication requirement (sources disagree)**: CVE Brief says "authenticated attackers," while KEV says only "remote attackers," with no authentication condition. None of the sources reviewed says which key or role is required.
- **Fixed version**: CVE Brief lists the affected range as before 1.83.10 and recommends upgrading to **1.83.10 or later**. The 1.83.10 release notes (2026-04-27) include "Replace `custom_code` sandbox with RestrictedPython" but do not name the CVE; the link between the two is this article's inference.
- **Exploitation status**: CISA has confirmed exploitation. CVE Brief says a public PoC is on GitHub and Nuclei has detection templates. The Hacker News linked this KEV batch to ransomware, cryptomining, and LLMjacking attacks, but that article could not be read this time, so **what attackers actually do with this flaw could not be verified**.
- **Response**: upgrade to 1.83.10 or later (the current LTS is 1.108.x); restrict the LiteLLM proxy to trusted internal sources; check logs for calls to `/guardrails/test_custom_code`, especially from non-admin accounts. A LiteLLM proxy usually holds API keys for several LLM providers; if you suspect compromise, rotate those keys as well.

### pam-MySQL: accounts with NULL passwords log in with any password (CVE-2026-124749)

On **Nov 19**, researcher Andrey Vasilevsky disclosed an authentication bypass in pam-MySQL (the Debian/Ubuntu package is libpam-mysql) on the oss-security mailing list. Red Hat assigned the CVE.

- **Root cause**: pam-MySQL inverts the `PAM_DISALLOW_NULL_AUTHTOK` flag that OpenSSH passes in (at both call sites in `pam_sm_authenticate`). Accounts whose password column is SQL NULL **pass authentication without any password comparison**, so an unauthenticated network attacker can log in with any password.
- **Trigger conditions**: sshd passes this flag under the **default** `PermitEmptyPasswords no`, so default settings are affected. The attacker only needs to send a non-empty password. Only SSH is confirmed affected; no source confirms whether FTP, mail, or other services using pam-MySQL pass this flag.

| Version line | Exploitable rows | Main distributions |
|---|---|---|
| 0.8.x | Password is NULL (empty string not affected) | Debian, Ubuntu, FreeBSD, Gentoo, Kali, and others |
| 1.0 beta | Password is NULL **or an empty string** | Fedora, Nix, Mageia, ALT, and others |

Because 1.0 beta is exploitable with empty strings too, schemas like PostfixAdmin's and Froxlor's, which define the password column as `NOT NULL DEFAULT ''` or `NOT NULL`, may also be affected.

- **Score**: CVSS 3.1 9.8 is the researcher's own score (`AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`). He also says 8.1 is reasonable if the database-schema precondition is priced into attack complexity. NVD, Debian, and Ubuntu have not published scores.
- **Fix status (only partly patched)**:

| Platform | Status |
|---|---|
| Debian trixie | Fixed in 0.8.2-2.1+deb13u1 (DSA-6643-1) |
| Debian bookworm | Fixed in 0.8.2-2+deb12u1 (DLA-4919-1) |
| Debian forky/sid | Not yet fixed |
| Ubuntu (16.04–26.10) | "Needs evaluation"; no fix yet |
| Upstream 1.0 (master) | Fix pushed on 11/19, but **no new release** (latest is still 1.0.0-beta3) |
| Upstream 0.8 branch | Not updated; relies on distribution patches |
| Fedora, FreeBSD, Gentoo, and others | Not checked in this research |

A news headline says the flaw is "fixed in 0.8.2-2.1", but 0.8.2-2.1 is an **affected** version; the fixed version is 0.8.2-2.1+deb13u1.

- **Mitigation (do this even before patching)**:
  - Find and purge accounts whose password is NULL **or an empty string** in every pam-MySQL authentication table, for example `SELECT username FROM users WHERE password IS NULL OR password='';` (adjust table and column names to your environment).
  - Change the password column to `NOT NULL` and do **not** give it an empty-string default (on 1.0 beta, empty strings are exploitable too).
  - Do **not** set sshd to `PermitEmptyPasswords yes`: it makes NULL rows get denied, but it turns off OpenSSH's empty-password protection and lets empty-string passwords log in instead.
  - The `nullok` option added by the fix is off by default; do not enable it.
- **Hard to detect**: OpenSSH logs only "Accepted password for" for both a bypass and a genuine login, so the two cannot be told apart. The way to tell is the database: if an account's password was NULL or an empty string at the time and a password login succeeded, that is a bypass. But the database's current state does not show its past state, so you need binlogs or backups. pam-MySQL's audit table is off by default, and one of its failure paths writes the misspelled "AUTHENTICATION FALURE", so a search for "FAILURE" will miss it.
- **Exploitation status**: No exploitation in the wild seen; the researcher's reproducer is available only on request; not on CISA KEV.

## Other November KEV entries (verify item by item)

CISA's November KEV updates include GPUStack, SignalWire FreeSWITCH, OpenSSH, and IBM Aspera Faspex (11/9), plus Barracuda Email Security Gateway (CVE-2026-116606, CVSS v4.0 9.3, added 11/10), Microsoft Outlook, Google Chrome, Cisco BroadWorks, and Openwave Webtop (11/10). A SonicWall SSLVPN authentication bypass was added on 11/6, and two Citrix NetScaler CVEs were also added. Of the four added on 11/18, BerriAI LiteLLM (CVE-2026-40217) is covered in the "Other notable items" section above. The Barracuda CVE-2026-116606 is listed in the key CVE table above. For the rest, secondary sources disagree on which CVE maps to which product, so **this article does not list individual identifiers.** Check the [CISA KEV catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog) before scheduling patches.

## Items not confirmed

- **jQuery ReDoS (iThome report):** The report and the jQuery official blog agree, and the details are in the jQuery section below. Neither mentions a CVE identifier, and this research found none, so the article says so.
- **Tails upstream fix and GHSA content:** The GHSA page could not be opened, so the fixed version and date remain to be confirmed.
- **Chaining NGINX with the kernel SCTP flaw:** Described only by Xint; the kernel flaw has no CVE, and Censys says it has not verified the chain.
- **NGINX fix status on RHEL and Rocky Linux:** Comes only from GetPageSpeed; not checked directly with Red Hat.
- **FastUnlock's real impact:** Sources disagree on WsiAccount's privileges, whether administrator rights are reachable, and whether Windows 10 is affected.

## jQuery: ReDoS fixed in 4.1.0 and 3.8.0, no CVE identifier seen

On November 18, 2026, jQuery released 4.1.0 and 3.8.0. Both fix a regular-expression denial-of-service (ReDoS) issue that could cause a page to stop responding. Sources: [iThome report](https://www.ithome.com.tw/news/180617) and [the jQuery official blog](https://blog.jquery.com/).

The problem was in how jQuery parses CSS selectors. The old regular expression, when given a long run of consecutive hexadecimal escape characters followed by an invalid character, kept re-matching repeatedly, consuming CPU until the browser or server-side render stalled. Both new releases revise the character-matching rules.

**Release strategy:** 3.8.0 is the last planned feature release in the 3.x line. From now on, 3.x receives only critical security and bug fixes, and new features go into 4.x. 3.8.0 also includes fixes that accumulated on the 3.x branch over several years but had not been formally released, and marks some older APIs removed from 4.x as deprecated, so that jQuery Migrate can flag upgrade compatibility issues.

**CVE status:** The report does not mention a CVE identifier, and this research found none for this issue. The point is that **no CVE identifier does not mean no risk.**

The lack of a CVE identifier matters because:

- The NVD and most vulnerability scanners create entries from CVEs, so issues without one are easier for inventory tools to miss.
- A company that patches only what scanners report may wrongly conclude it has no known vulnerability.
- Inventory should therefore be based on library versions and vendor fix records, not on whether a CVE number exists.

Note that ReDoS issues in the jquery-validation plugin do have CVE records: CVE-2021-21252 (before 1.19.3), CVE-2021-43306 (the `url2` method, before 1.19.4), and CVE-2022-31147 (before 1.19.5, an incomplete fix for 43306). Separately, Aikido published a similar pre-CVE report in October 2025; whether it is the same issue as CVE-2021-43306 has not been confirmed. If you use jquery-validation, check these versions too.

Recommended steps:

- Inventory the jQuery and jquery-validation versions loaded by your front-end pages, and record where each comes from (CDN, package manager, or inline file).
- If you use jQuery 3.x, upgrade to 3.8.0; if you use 4.x, upgrade to 4.1.0. After 3.8.0, 3.x only receives critical security and bug fixes. Check compatibility with jQuery Migrate before upgrading.
- If you still use jquery-validation, upgrade to at least 1.19.5.
- Check whether user-controlled input reaches validation rules such as `url2`, and limit input length as an interim measure.

## Enterprise patch priorities

| Role | First actions |
|---|---|
| Virtualization administrators | **Top priority:** upgrade vCenter to 8.0 U3m, 9.0.2.0200, 9.1.1.0200, or VCF 5.2.5 (exploited; CISA KEV due Nov 23); restrict management-interface access; hunt for unknown SSO administrators and SSH. |
| AI platform operations | Upgrade the LiteLLM proxy to 1.83.10 or later (exploited); restrict it to internal access; review calls to `/guardrails/test_custom_code`, and rotate LLM API keys if you suspect compromise. |
| Linux account management | Check whether pam-MySQL (libpam-mysql) is used for SSH or other authentication; purge NULL or empty-string password rows from authentication tables; on Debian, apply DSA-6643-1 / DLA-4919-1. |
| System administrators | Check whether Apache httpd has HTTP/2 enabled, and upgrade to 2.4.71 or disable h2 first; inventory NGINX versions and whether HTTP/2, HTTP/3, and the mail module are enabled; upgrade to 1.30.7 or 1.31.9 or later (for distribution packages, go by each distribution's advisory) and **restart**; temporarily block SCTP module autoloading. |
| PHP operations | Upgrade to 8.5.13 / 8.4.28 / 8.3.37 / 8.2.36 and restart FPM; check FastCGI connection reuse, `session.upload_progress.enabled`, and `catch_workers_output`; plan upgrades for 8.1 and older. |
| Back end and DevOps | Inventory OpenJDK and Ruby versions; upgrade Java to Oracle's or your vendor's November build and Ruby to 4.0.10 / 3.4.13 / 3.3.14; update container images, Lambda, and CI runners too. |
| Self-hosted service operators | Track updates for products that bundle Ruby, such as GitLab, Mastodon, and Discourse; restrict access with a VPN or IP allowlist until patched. |
| Endpoint management | Switch laptop BitLocker to TPM + startup PIN; disable AutoPlay for removable media; tell users to shut down or hibernate when leaving. |
| Security staff | Schedule PHP and other listed KEV items per CISA's catalog; retain NGINX error logs showing workers exiting on signal, for reference; inventory the Ruby and jQuery issues that have no CVE. |
| General users | Update Tails to 7.17.1 or later; restart Tails; avoid using the extension's element picker on untrusted sites. |
| Developers | Upgrade pip in venvs, container images, and CI to 26.2.2 or later; check whether untrusted data is passed to `java.util.Base64`; check whether Ruby code handles untrusted strings in non-UTF-8 encodings or compiles user-supplied regexes. |

You can check versions with these read-only commands, but version strings do not replace vendor patch notes:

```bash
nginx -V 2>&1 | head -1
java -version
uname -m
php -v
ruby -v
httpd -v 2>/dev/null || apache2 -v
python -m pip --version
```

### Patch and response checklist

- [ ] Confirm the affected ranges in nginx.org's advisories, and whether HTTP/2, HTTP/3, and the mail module are enabled.
- [ ] Upgrade NGINX to 1.30.7 or 1.31.9 or later, and fully restart the service (not just reload).
- [ ] If you cannot upgrade immediately, temporarily set `http2 off;`, and block external access to QUIC or mail listeners.
- [ ] Inventory OpenJDK versions and CPU architecture (x86-64 AVX-512 and ARM are affected differently), and restart all Java processes after upgrading.
- [ ] Confirm the CVE-2026-114938 fix list on Oracle's official page (not verified in this article).
- [ ] Upgrade PHP to 8.5.13, 8.4.28, 8.3.37, or 8.2.36 (including environments upgraded in October), restart PHP-FPM, and rebuild container images.
- [ ] If you do not need upload progress, keep `session.upload_progress.enabled=0` in every configuration that shares a session store (set in php.ini or the FPM pool); this blocks only one PHPAfterShell route, so you still need to upgrade.
- [ ] On platforms with no fixed packages yet, such as RHEL, track vendor updates and consider moving sessions to a database or Redis backend and limiting the length of user strings written to the session.
- [ ] Check whether the front end reuses FastCGI connections (`fastcgi_keep_conn on`, `enablereuse=on`), and turn it off until patched.
- [ ] If you use the official PHP-FPM Docker images, check the `catch_workers_output` setting and rebuild the images.
- [ ] Confirm through your distribution's advisory whether its NGINX package has the backported fix (RHEL and Rocky Linux had none as of Nov 20), and block SCTP module autoloading on hosts.
- [ ] If you use products that embed NGINX, such as ingress-nginx, OpenResty, or Tengine, check for a fix; if there is none, turn off HTTP/2 for now.
- [ ] Upgrade Barracuda ESG firmware to 9.4.0.030 or later, and check for unauthorized configuration-import records.
- [ ] Using Oracle's official risk matrices, schedule patches for the CVSS 9.0+ items in the November CSPU across Database Server, WebLogic Server, Access Manager, and Service Bus.
- [ ] Schedule patches for all listed items per the CISA KEV catalog.
- [ ] Inventory front-end jQuery and jquery-validation versions; do not rely on CVE identifiers to decide whether you are affected.
- [ ] Tails users: update to 7.17.1 or later, restart, and back up Persistent Storage if needed.
- [ ] Upgrade vCenter to the versions listed in VMSA-2026-0009 (including systems with the July fix), and check SSO accounts, SSH, and unusual sessions.
- [ ] Upgrade SDDC Manager and VMware Tools for Windows per VMSA-2026-0009.
- [ ] Upgrade Ruby to 4.0.10, 3.4.13, or 3.3.14, restart application servers, and rebuild container images; plan upgrades for branches 3.2 and earlier.
- [ ] Check vendor update status for self-hosted products that bundle Ruby (GitLab, Mastodon, and others), and restrict external access until patched.
- [ ] If you use AWS WAF, consider enabling the Ruby2Shell rules in Known Bad Inputs version 1.29 (Count first, then Block).
- [ ] Upgrade the LiteLLM proxy to 1.83.10 or later, restrict external access, and review calls to `/guardrails/test_custom_code` (CISA KEV, due 12/2).
- [ ] If Apache httpd has HTTP/2 enabled, upgrade to 2.4.71 (for distribution packages, go by each distribution's advisory); if you cannot upgrade right away, disable h2 first.
- [ ] Upgrade pip to 26.2.2 or later in every environment, including old venvs, container images, and CI runners.
- [ ] pam-MySQL users: purge accounts whose password is NULL or an empty string from authentication tables and set the column to `NOT NULL` (with no empty-string default), apply the fix on Debian, and keep sshd at `PermitEmptyPasswords no`.
- [ ] Windows endpoints: switch BitLocker to TPM + startup PIN, disable AutoPlay for removable media, and track Microsoft's fix for FastUnlock.

## Conclusion

November's risk falls into three groups. The first is memory-safety bugs in foundational components such as NGINX, OpenJDK, PHP, and Ruby. They affect a wide range of systems, and most require a restart or rebuild before a fix takes effect. The second is items with real exploitation records: **vCenter's CVE-2026-123890 (CVSS 9.8) was exploited for about two months before the fix, and CISA gave only 3 days to patch**, making it this month's top priority; besides upgrading you need to check for compromise. KEV items such as LiteLLM and PHP should also be handled first. The third is issues with no CVE or no fix yet (Ruby's other six flaws, jQuery, FastUnlock), which CVE-based scanning alone will miss; inventory them yourself by version and configuration. Verify assets against official advisories first, then schedule upgrades to reduce real risk.

## Fact-check record

**Checked on 2026-11-20 (Taiwan time); the Ruby, VMware, Windows Narrator, PHP November 19 release, and NGINX follow-up sections on 2026-11-21; PHPAfterShell, Apache HTTP Server, pip, LiteLLM, pam-MySQL, and vCenter's KEV status on 2026-11-22.**

### Verified (from nginx.org or vendor advisories, or cross-checked with credible sources)

| Item | Result | Source |
|---|---|---|
| NGINX 10 CVEs and fixed versions | nginx.org lists the CVEs and affected ranges; stable 1.30.7 and mainline 1.31.9 are fixed | [NGINX](https://nginx.org/en/security_advisories.html) |
| CVE-2026-123007 public PoC conditions | Described by secondary sources (Tenable, Censys); no ITW exploitation seen | [Tenable](https://www.tenable.com/blog/nginx2root-cve-2026-123007-frequently-asked-questions-about-five-critical-nginx), [Censys](https://censys.com/advisory/nginx2root) |
| CVE-2026-114938 fixed versions | Oracle's page could not be read; secondary sources list 17.0.21.1 and others | [Tenable](https://www.tenable.com/blog/java4shell-cve-2026-114938-frequently-asked-questions-about-openjdk-rce-vulnerability), [Equixly](https://equixly.com/blog/2026/11/17/cve-2026-114938-pre-auth-heap-overflow-in-java-17-21-and-25/) |
| Three Oracle Database Server CVSS 3.1 9.9 items (CVE-2026-114819, CVE-2026-114822, CVE-2026-114848) | From Oracle's official text-form risk matrix ([cspunov2026verbose](https://www.oracle.com/security-alerts/cspunov2026verbose.html)), supplied by the user; version ranges and vectors as listed | [Oracle](https://www.oracle.com/security-alerts/cspunov2026verbose.html) |
| Oracle WebLogic Server, Access Manager, and Service Bus items with CVSS ≥ 9.0 (CVE-2026-114862, 91456, 91469, 91470, 91500, 91507, 91510, 91561, 91569, 91570, 91583) | From the same official text-form matrix supplied by the user; the score for CVE-2026-91585 was cut off in the excerpt and is excluded | [Oracle](https://www.oracle.com/security-alerts/cspunov2026verbose.html) |
| Tails 7.17.1 release date and contents | Nov 17; removes uBlock Origin; kernel 6.12.117 | [Linuxiac](https://linuxiac.com/?p=223307) |
| PHP November 19 releases, the 17 GHSAs, and the CVSS scores and conditions of the critical items | php.net announcements and ChangeLog; each critical item's score and conditions checked against its GHSA page (some Moderate items' GHSAs not read) | [php.net](https://www.php.net/archive/2026.php), [GHSA](https://github.com/php/php-src/security/advisories) |
| PHPAfterShell (CVE-2026-126714) mechanism, exploitation conditions, and mitigation limits | GHSA text; Wiz, Ostorlab, and Cyber Kendra agree | [GHSA](https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp), [Ostorlab](https://blog.ostorlab.co/phpaftershell-php-session-file-rce-cve-2026-126714.html) |
| CVE-2026-119618 severity, affected and fixed versions | Apache's vulnerability page and BleepingComputer agree | [Apache httpd](https://httpd.apache.org/security/vulnerabilities_24.html), [BleepingComputer](https://www.bleepingcomputer.com/news/security/apache-http-server-patches-critical-http-2-remote-code-execution-flaw/) |
| CVE-2026-40217 KEV listing (11/18, due 12/2) and description | CISA KEV JSON | [CISA KEV](https://www.cisa.gov/known-exploited-vulnerabilities-catalog) |
| CVE-2026-124749 root cause, conditions, mitigation, and Debian fixed versions | The original oss-security post and the Debian tracker; Ubuntu's page shows "Needs evaluation" | [oss-security](https://seclists.org/oss-sec/2026/q4/788), [Debian](https://security-tracker.debian.org/tracker/CVE-2026-124749), [Ubuntu](https://ubuntu.com/security/CVE-2026-124749) |
| pip 26.2.2 release date and certifi update | pip changelog and PyPI release history | [pip changelog](https://pip.pypa.io/en/stable/news/), [PyPI](https://pypi.org/project/pip/#history) |
| PHPAfterShell fix status by platform | Per Precursor Security's live roundup (Nov 20); distribution trackers not checked one by one | [Precursor](https://www.precursorsecurity.com/blog/phpaftershell-critical-php-rce-vulnerabilities) |
| Censys's reproduction of CVE-2026-123007 | Censys blog: reproduced only the flow-control accounting error, with no crash and no RCE (corrects the original text) | [Censys](https://censys.com/blog/nginx2root-simple-test/) |
| NGINX fixed packages for Debian and Ubuntu | Distribution tracker pages | [Debian](https://security-tracker.debian.org/tracker/CVE-2026-123007), [Ubuntu](https://ubuntu.com/security/CVE-2026-123007) |
| Ruby's seven flaws, GHSA identifiers, and fixed versions | Ruby advisory published Nov 18; fixed in 4.0.10, 3.4.13, 3.3.14; Ruby uses GHSA only, CVEs not yet assigned | [Ruby](https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/) |
| CVE-2026-132825 mapping to GHSA-34m4-m9fh-gqp5, Rails/Sinatra reachability, downstream products | AWS and Aikido agree | [AWS](https://aws.amazon.com/security/security-bulletins/2026-193-aws/), [Aikido](https://www.aikido.dev/blog/ruby2shell) |
| VMSA-2026-0009's five CVEs, CVSS, fixed versions, no workaround, Nov 20 revision | Broadcom advisory and official Q&A | [Broadcom](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495), [Q&A](https://github.com/vmware/vcf-security-and-compliance-guidelines/blob/main/security-advisories/vmsa-2026-0009/README.md) |
| CVE-2026-123890 added to CISA KEV (Nov 20, due Nov 23, forensic triage required) | CISA alert and KEV JSON (catalogVersion 2026.11.20); confirms the earlier single-source (KBY) report | [CISA alert](https://www.cisa.gov/news-events/alerts/2026/11/20/cisa-adds-four-known-exploited-vulnerabilities-catalog) |
| CVE-2026-123890 exploitation | Help Net Security and Rapid7 relaying Google/Mandiant; Broadcom does not mention it; Google's original not checked directly | [Help Net Security](https://www.helpnetsecurity.com/2026/11/20/vmware-vcenter-zero-day-cve-2026-123890-exploited/), [Rapid7](https://www.rapid7.com/blog/post/etr-cve-2026-123890-critical-authentication-bypass-vmware-vcenter/) |
| FastUnlock prerequisites, tested version, and no-CVE status | Three news sources agree; the researcher's GitHub and ThreatLocker's post not checked directly | [Cyber Security News](https://cybersecuritynews.com/windows-11-narrator-lock-screen-0-day/), [HWBusters](https://hwbusters.com/news/fastunlock-zero-day-turns-windows-11s-narrator-into-a-way-past-the-lock-screen-on-bitlocker-pcs/), [GBHackers](https://gbhackers.com/new-windows-11-zero-day-vulnerability/) |

### Pending and excluded

| Lead | Reason |
|---|---|
| jQuery ReDoS, November 2026 CVE | No source found; not included. |
| jQuery 4.1.0 / 3.8.0 ReDoS (iThome report, 2026-11-18) | Report retrieved with curl (an earlier subagent fetch returned 403); consistent with the jQuery official blog; no CVE identifier seen. |
| Java4Shell "pre-auth RCE in Jira, Confluence, Jenkins, Keycloak" | Single-source claim from Calif; RCE chain not public; not used. |
| CVE-2026-114938 official CVSS v3.1 score | Oracle's page returned 403; only 8.1 from OpenJDK and secondary sources is available. |
| uBlock Origin fixed version (1.75.4 or 1.76.4) | Sources conflict; GHSA page could not be opened; not used. |
| CVE mapping for November KEV items | Secondary sources disagree; individual identifiers not listed. |
| Barracuda CVE-2026-116606 score and exploitation status | Sources give 9.3 and 9.8; exploitation details conflict. The table uses the KEV finding; verify details against CISA's original. |
| pam-MySQL CVSS 9.8 | The researcher's own score only; NVD, Debian, and Ubuntu have not scored it. |
| pam-MySQL "fixed in 0.8.2-2.1" (SecurityOnline headline) | The Debian tracker shows 0.8.2-2.1 as affected and the fix as 0.8.2-2.1+deb13u1; the headline's claim is not used. |
| DSA-6643-1 release date (Nov 19 or Nov 20) | Two news sources disagree; the Debian announcement itself was not read. |
| pam-MySQL impact on services other than SSH | Any application that passes `PAM_DISALLOW_NULL_AUTHTOK` is affected, but only OpenSSH is confirmed to pass it. |
| LiteLLM fixed version 1.83.10 | CVE Brief recommends upgrading to 1.83.10; the release notes include the sandbox rewrite but not the CVE, so the mapping is inferred. |
| Whether LiteLLM requires authentication; what attackers actually do | CVE Brief says "authenticated," KEV says only "remote"; THN's LLMjacking and cryptomining report could not be read. |
| Nature of "compromised" in the pip CVE, and the GHSA | CVE Brief links a GHSA, but pip's advisories page shows no published advisory; details of the eMudhra incident were not checked. |
| PHPAfterShell public PoC | CSIRT Italia and HKCERT say one is public but give no link; depthfirst published only a harmless demonstration, and Precursor could not confirm one. This article lists both accounts. |
| PHPAfterShell discoverer | depthfirst says it found and named the flaw; the GHSA credits zplinn as reporter. |
| Whether PHPAfterShell affects 8.1 and older | The GHSA does not list 8.1; Cycode and depthfirst disagree. Unresolved. |
| Total PHP advisory count (17 or 18) | 17 GHSAs plus CVE-2026-48841 (a uriparser upgrade with no GHSA) make 18 CVE identifiers; this article uses 17 advisories. |
| Some PHP flaws affecting older branches (HeroDevs) | HeroDevs says CVE-2026-129481 and CVE-2026-129474 affect older branches such as 7.x, which conflicts with the GHSA affected ranges; not used. |
| Number of public NGINX PoCs | SecurityWeek says Censys also published a PoC; Censys describes its release as test traffic, not an exploit. This article follows Censys. |
| Ubuntu 26.10 NGINX fixed version 1.30.4-7ubuntu1.2 | Marked fixed on Ubuntu's page without explanation; not included in the table. |
| Ruby2Shell CVSS score | Search summaries showed 8.1 and 7.4, but none of the Ruby, AWS, or Aikido pages reviewed list a number; not used. |
| Whether the Ruby affected range goes back to 2.4.0 | Only Aikido says so; Ruby's advisory lists only maintained branches. |
| Whether VMware Tools 11.x is affected | Mentioned by Broadcom's Q&A and Rapid7; the response matrix lists only 12.3.x and later and 13.x. |
| FastUnlock can create an admin account or read browser credentials | From a Tom's Hardware citation and a vendor marketing page respectively; other sources say this is unproven; not used. |
| CVE-2026-58635 details | The MSRC page renders with JavaScript and its content could not be read; this article only notes it is unrelated to FastUnlock. |
| Other Oracle November CSPU CVSS 10.0 CVE identifiers (not Database Server) | The remaining IDs (CVE-2026-114835, CVE-2026-114784, CVE-2026-114824) come only from secondary sources and do not appear in the matrix excerpts verified so far; not verified. |

## References

Sources were accessed on **2026-11-20 to 11-22 (Taiwan time)**. Advisories may be updated later.

- [NGINX Security Advisories](https://nginx.org/en/security_advisories.html)
- [Wiz: NGINX HTTP/2 RCE vulnerabilities](https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities)
- [Tenable: nginx2root FAQ](https://www.tenable.com/blog/nginx2root-cve-2026-123007-frequently-asked-questions-about-five-critical-nginx)
- [CERT-EU 2026-022](https://cert.europa.eu/publications/security-advisories/2026-022/)
- [Censys: nginx2root advisory](https://censys.com/advisory/nginx2root)
- [Tenable: Java4Shell FAQ](https://www.tenable.com/blog/java4shell-cve-2026-114938-frequently-asked-questions-about-openjdk-rce-vulnerability)
- [Equixly: CVE-2026-114938 technical analysis](https://equixly.com/blog/2026/11/17/cve-2026-114938-pre-auth-heap-overflow-in-java-17-21-and-25/)
- [The Hacker News: Oracle November patches](https://thehackernews.com/2026/11/oracle-to-patch-11-java-flaws-today-as.html)
- [Linuxiac: Tails 7.17.1](https://linuxiac.com/?p=223307)
- [iThome: jQuery 4.1.0 and 3.8.0 ReDoS](https://www.ithome.com.tw/news/180617)
- [jQuery official blog](https://blog.jquery.com/)
- [Ruby: Multiple vulnerabilities in Regexp and String](https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/)
- [AWS Security Bulletin 2026-193-AWS: CVE-2026-132825](https://aws.amazon.com/security/security-bulletins/2026-193-aws/)
- [Aikido: Ruby2Shell](https://www.aikido.dev/blog/ruby2shell)
- [Broadcom: VMSA-2026-0009](https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39495)
- [Broadcom: VMSA-2026-0009 Q&A](https://github.com/vmware/vcf-security-and-compliance-guidelines/blob/main/security-advisories/vmsa-2026-0009/README.md)
- [Rapid7: CVE-2026-123890](https://www.rapid7.com/blog/post/etr-cve-2026-123890-critical-authentication-bypass-vmware-vcenter/)
- [Help Net Security: vCenter zero-day exploited](https://www.helpnetsecurity.com/2026/11/20/vmware-vcenter-zero-day-cve-2026-123890-exploited/)
- [Cyber Security News: Windows 11 Narrator lock-screen zero-day](https://cybersecuritynews.com/windows-11-narrator-lock-screen-0-day/)
- [HWBusters: FastUnlock](https://hwbusters.com/news/fastunlock-zero-day-turns-windows-11s-narrator-into-a-way-past-the-lock-screen-on-bitlocker-pcs/)
- [GBHackers: Windows 11 zero-day](https://gbhackers.com/new-windows-11-zero-day-vulnerability/)
- [PHP 2026 security advisories](https://www.php.net/archive/2026.php)
- [PHP 8 ChangeLog](https://www.php.net/ChangeLog-8.php)
- [php-src GitHub Security Advisories](https://github.com/php/php-src/security/advisories)
- [Apache HTTP Server 2.4 vulnerabilities](https://httpd.apache.org/security/vulnerabilities_24.html)
- [BleepingComputer: Apache HTTP Server patches critical HTTP/2 RCE](https://www.bleepingcomputer.com/news/security/apache-http-server-patches-critical-http-2-remote-code-execution-flaw/)
- [CVE Brief: CVE-2026-133949 (pip)](https://cvebrief.com/cve/cve-2026-133949/)
- [pip changelog](https://pip.pypa.io/en/stable/news/)
- [pip HTTPS certificates](https://pip.pypa.io/en/stable/topics/https-certificates/)
- [oss-security: CVE-2026-124749 pam-mysql](https://seclists.org/oss-sec/2026/q4/788)
- [Debian: CVE-2026-124749](https://security-tracker.debian.org/tracker/CVE-2026-124749)
- [Ubuntu: CVE-2026-124749](https://ubuntu.com/security/CVE-2026-124749)
- [CISA: four KEV additions on Nov 20](https://www.cisa.gov/news-events/alerts/2026/11/20/cisa-adds-four-known-exploited-vulnerabilities-catalog)
- [CVE Brief: CVE-2026-40217 (LiteLLM)](https://cvebrief.com/cve/cve-2026-40217/)
- [LiteLLM v1.83.10 release notes](https://docs.litellm.ai/release_notes/v1.83.10/v1-83-10)
- [GHSA-fm2m-fjf5-v3cp: CVE-2026-126714](https://github.com/php/php-src/security/advisories/GHSA-fm2m-fjf5-v3cp)
- [Precursor Security: PHPAfterShell live updates](https://www.precursorsecurity.com/blog/phpaftershell-critical-php-rce-vulnerabilities)
- [Wiz: PHPAfterShell](https://www.wiz.io/blog/phpaftershell-critical-php-rce-vulnerabilities-cve-2026-126714)
- [Ostorlab: PHPAfterShell](https://blog.ostorlab.co/phpaftershell-php-session-file-rce-cve-2026-126714.html)
- [Cyber Kendra: PHPAfterShell](https://www.cyberkendra.com/2026/11/phpaftershell-cve-2026-126714-php-rce.html)
- [PHP Architect: PHP's November security release](https://phparch.com/blog/phps-november-security-release-seven-critical-fixes-explained)
- [Censys: nginx2root simple test](https://censys.com/blog/nginx2root-simple-test/)
- [Xint: NGINX2Root](https://xint.io/blog/nginx2root-remote-code-execution)
- [GetPageSpeed: NGINX2Root checker and fix](https://www.getpagespeed.com/nginx2root)
- [SecurityWeek: F5 patches NGINX2Root](https://www.securityweek.com/f5-patches-critical-nginx2root-flaws-as-poc-exploits-go-public/)
- [Debian: CVE-2026-123007](https://security-tracker.debian.org/tracker/CVE-2026-123007)
- [Ubuntu: CVE-2026-123007](https://ubuntu.com/security/CVE-2026-123007)
- [CISA Known Exploited Vulnerabilities Catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog)
- [Previous article: October 2026 security advisories]({% link _posts/en/2026-10-23-october-critical-cve-security-incidents.md %})
