Linux NoisyTCP CVE-2026-99288 + 2 more
Vulnerability Digest Nov 16, 2026
Linux NoisyTCP CVE-2026-99288 can crash servers remotely without login; no CVSS yet. Also Apache Shiro CVE-2026-129349, uBlock Origin XSS. No exploitation.
This digest picks items from November 14-15 that matter to small and mid-sized companies. The top priority is NoisyTCP (CVE-2026-99288), a TCP handling flaw in the Linux kernel. It can be triggered remotely without authentication and, when it succeeds, causes a kernel panic (the machine goes down). Servers running Nginx, Apache or SSH in their default configuration are in scope. NVD has no CVSS score yet and no public exploit code exists. Because almost every Linux distribution is affected, start by checking the kernel update schedule of your own and your vendors' Linux servers.
Also covered: Apache Shiro (CVE-2026-129349, CVSS v4.0 9.1), where any password works once authentication caching is enabled, and a universal XSS in the uBlock Origin browser extension (GHSA-cmqw-9r2w-6wv2, severity High). In this digest, "exploited" means listed in CISA's KEV catalog or confirmed by the vendor. None of today's three items qualify, so exploitation confirmed: 0.
Today's vulnerabilities
| Product | CVE | Severity (CVSS) | Exploitation | Fix |
|---|---|---|---|---|
| Linux kernel (NoisyTCP) | CVE-2026-99288 | Not yet in NVD (Received) | No public exploit; no exploitation reports found | Distribution kernel updates (Debian: bookworm 6.1.192-1, trixie 6.12.117-1, etc.). Mitigations available |
| Apache Shiro | CVE-2026-129349 | CVSS v4.0 9.1 (Apache) | No reports found | 3.0.1 or later. Workaround: disable authenticationCachingEnabled |
| uBlock Origin (browser extension) | No CVE (GHSA-cmqw-9r2w-6wv2) | Severity High (no CVSS) | No reports found | 1.75.4 or later |
Linux kernel NoisyTCP CVE-2026-99288: a TCP race that can crash the kernel remotely
On November 15 (early on the 16th in Japan), the finder, Hyunwoo Kim, published details on oss-security. When the kernel looks up TCP connection state, several CPUs working at once can mix up a socket that was already freed. The report describes two trigger flows.
- Flow 1: a freed request socket is reallocated at the same address, and the new one has no listener attached (NULL). The receive path dereferences it and the kernel panics. This is a remote denial of service
- Flow 2: a mix-up involving a full child socket can lead to a remote use-after-free. It needs complex races to succeed in a nested way and is hard to trigger without special techniques
Why it matters. The report says that if the DoS hits a web server running in a container, the whole host goes down, not just the application. It can also be triggered pre-auth against default Nginx, Apache and SSH servers that attacker packets can reach directly. Packet processing must be spread across contexts, though: two or more RX queues, or RPS distributing packets across CPUs.
How easy is it? It varies a lot by environment. The report says it took 5 seconds to 2 minutes on VMs such as QEMU/KVM, but about 14 hours against a quiet bare-metal server (8 RX queues) even with an exploit tuned for the target. We found no public exploit code and no reports of exploitation, so we cannot say it is being exploited.
Affected range. Introduced by commit 079096f103fa (2015-10-03); fixed by mainline commit 4e2b3ef19e0e (2026-11-03). It lay dormant for about 11 years and is reported to affect almost all distributions. NVD has an entry but no CVSS yet (status: Received).
Fix status differs by distribution. As of November 16, the Debian security tracker shows the following.
| Debian release | Fixed version | Note |
|---|---|---|
| bookworm (12) | 6.1.192-1 | DLA-4906-1; fixed in the security update |
| trixie (13) | 6.12.117-1 | DSA-6628-1; fixed in the security update |
| forky | 7.2.15-1 listed as vulnerable | No fix listed |
| sid (unstable) | 7.3.4-1 | Fixed |
Ubuntu's CVE page lists the priority as Medium, but the linux packages from 26.10 down to 14.04 were all "Needs evaluation" and showed no fixed version. We did not check Red Hat-family distributions, so see each vendor's advisory. Compare uname -r against the fixed version.
How to check and respond. First, check the running kernel and whether updates are available.
# Running kernel version
uname -r
# Debian / Ubuntu: installed kernel packages and pending updates
dpkg -l 'linux-image-*' | grep ^ii
apt list --upgradable 2>/dev/null | grep linux-image
# After updating, reboot to run the new kernel
sudo rebootIf a fixed kernel is available, update and reboot; otherwise the old kernel keeps running. If no fix is available yet, or you cannot reboot immediately, the finder lists two temporary mitigations. Both have side effects, so understand them before use.
# Mitigation 1: disable SYN cookies (reverts on reboot; per network namespace)
sudo sysctl -w net.ipv4.tcp_syncookies=0
# Mitigation 2: reduce to a single RX queue and disable RPS / RFS (adjust the NIC name)
# Check RX queues: ethtool -l eth0- Mitigation 1 blocks the path that rebuilds a request socket from a SYN cookie. It is set per network namespace, so apply it to each container that has its own. Disabling it lowers SYN flood protection
- Mitigation 2 removes the concurrent-RX-context condition. It may reduce throughput, so be careful on heavily loaded servers
For managed cloud services, the provider updates the kernel. For virtual servers (EC2, Azure VMs and so on) you are responsible for OS updates, so ask your vendor about their schedule.
Apache Shiro CVE-2026-129349: with authentication caching on, any password works
Apache Shiro is a Java authentication and authorization library. NVD published this on November 15, with Apache (the CNA) scoring it CVSS v4.0 9.1. When authentication caching is enabled on DefaultLdapRealm (or JndiLdapRealm), after one successful login a user can log in again with any password, because the default AllowAllCredentialsMatcher used for cached credentials does not verify the password.
Note the condition. Only deployments that set authenticationCachingEnabled=true are affected, and that is not the default. A Shiro setup you have not changed is out of scope. All versions through 3.0.0 are affected and the fix is 3.0.1 or later. The workaround is to disable authenticationCachingEnabled.
How to check. Find the shiro-core version in your Java project. For a system built by a vendor, ask the developer to run the commands below. Also check the config (shiro.ini or Spring configuration) for authentication caching.
# Maven
mvn dependency:tree | grep shiro
# Gradle
./gradlew dependencies | grep shiro
# Config check (is authentication caching enabled?)
grep -rn "authenticationCachingEnabled" src/ config/If you use Shiro for LDAP authentication with caching on, internal admin consoles and business systems may be affected. Until you can update, disable authentication caching and restart. Details are in the NVD entry, the Apache mailing list post and the oss-security post.
uBlock Origin universal XSS: a malicious site drives the extension's element picker
In the ad blocker uBlock Origin, a crafted web page can embed the extension's element picker in an invisible iframe and, with one click from the user, add arbitrary trusted filters. Trusted filters can inject JavaScript, so the result is described as arbitrary JavaScript execution on any site (universal XSS). The GitHub advisory GHSA-cmqw-9r2w-6wv2 was published on November 15 with severity High. It has no CVE and no CVSS score.
Affected versions are 1.75.2 and lower; the fix is 1.75.4 (published November 3, and the advisory says it is live on AMO). According to the finder's write-up, the main target is the Firefox MV2 build. The advisory also mentions MV2 Chromium, and says uBO Lite (MV3) had a similar but less problematic issue. Check the advisory for differences by browser and version.
How to check. Look at the version in the extension manager: about:addons in Firefox, chrome://extensions in Chromium browsers. Confirm uBlock Origin is 1.75.4 or later. Extensions normally auto-update, but you can trigger a manual update check. If you manage extensions centrally, ask the administrator for a version list.
We found no reports of exploitation today. In a real attack, though, attacker code could run on other sites you are logged in to after you visit a malicious page. Updating takes minutes, so it is worth checking.
Checklist for non-IT staff: what to do today
- Ask IT or your vendor whether you have Linux servers (on-premises, cloud, VPS) and have them set a date for the kernel update and reboot
- For servers that cannot be updated right away, ask whether to use the finder's mitigations (such as disabling SYN cookies)
- Ask your developers or vendor whether any Java business system uses Apache Shiro. If so, request an update to 3.0.1 or later, or disabling authentication caching
- Ask staff who use uBlock Origin to confirm version 1.75.4 or later
- If none apply, record "not affected" and stop here
Related articles
- Previous digest (Citrix NetScaler and more)
- Linux kernel Copy Fail (CVE-2026-31431): impact check and mitigation
- Vulnerability assessment cost and how to choose
Sources
- oss-security (NoisyTCP): https://www.openwall.com/lists/oss-security/2026/11/15/2
- NVD CVE-2026-99288: https://nvd.nist.gov/vuln/detail/CVE-2026-99288
- Linux kernel fix commit: https://git.kernel.org/stable/c/4e2b3ef19e0e04adca38442f07dd6bc93c712bf1
- Debian security tracker: https://security-tracker.debian.org/tracker/CVE-2026-99288
- Ubuntu CVE page: https://ubuntu.com/security/CVE-2026-99288
- NVD CVE-2026-129349: https://nvd.nist.gov/vuln/detail/CVE-2026-129349
- Apache Shiro announcement (mailing list): https://lists.apache.org/thread.html/1whn52ht402lhc782c3s843c9hho8b4y
- oss-security (Shiro): http://www.openwall.com/lists/oss-security/2026/11/14/8
- uBlock Origin advisory GHSA-cmqw-9r2w-6wv2: https://github.com/gorhill/uBlock/security/advisories/GHSA-cmqw-9r2w-6wv2
- Finder's write-up: https://iter.ca/post/ubo-uxss/
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
FAQ
NoisyTCP has no CVSS score yet. Do we still need to hurry?
As of November 16 NVD has no CVSS, but the flaw is reported to be remotely triggerable without authentication and to take the server down. We found no exploitation reports or public exploit code, so there is no need to panic, but set a date for the kernel update and reboot soon.
Is disabling SYN cookies safe?
It is a mitigation suggested by the finder, with the side effect of weaker SYN flood protection. It is set per network namespace, so each container needs it, and it reverts on reboot. Use it only as a stopgap until you can install a fixed kernel, after consulting IT or your vendor.
Can we use Apache Shiro and still be unaffected?
Yes. Only setups with authenticationCachingEnabled=true on DefaultLdapRealm or JndiLdapRealm are affected. It is not the default, so if you have not changed it you are out of scope. Still, consider updating to 3.0.1 or later.
Should we remove uBlock Origin right away?
Removal is not required. Updating to the fixed 1.75.4 or later resolves the issue. Check the version in the extension manager and update if it is older.
株式会社オブライト
Oflight Inc. is a Tokyo-based IT company providing software development, digital signage, web development, network systems, and IoT/AR/VR technology services.
Related free tools (no sign-up, instant results)
Feel free to contact us
Contact Us