nginx CVE-2026-123007 + 9 more
Vulnerability Digest Nov 19, 2026
nginx HTTP/2 flaw CVE-2026-123007 (F5 CVSS 9.2) has a public PoC: update to 1.31.9/1.30.7 or disable HTTP/2. Also seven Ruby bugs and four KEV additions.
From information published or added on Nov 18, we picked the items most relevant to small-business systems. The top priority is the nginx HTTP/2 flow-control memory corruption (CVE-2026-123007). nginx.org rates it Major; F5 scores it CVSS v4.0 9.2 and v3.1 8.1. nginx with HTTP/2 enabled is affected, and unauthenticated remote code execution may be possible. Rapid7 has published a working proof-of-concept (PoC) on GitHub. Check the nginx version on your servers and your vendors' servers, and update to the fixed release (mainline 1.31.9 / stable 1.30.7). If you cannot update right away, you can work around it by disabling HTTP/2. None of the sources we checked reports exploitation in real attacks.
The same day, seven Ruby vulnerabilities were disclosed (one is reachable before authentication by default in Rails and classic Sinatra), and CISA added four entries to the KEV catalog (known exploited vulnerabilities): LiteLLM (CVE-2026-40217), Synology DSM (CVE-2024-10441), Apache Axis (CVE-2026-90436) and REDCap (CVE-2026-90817). In this digest, "exploitation confirmed" means listed in CISA KEV. Among the Nov 18 additions, four are confirmed exploited (nginx and Ruby are not in KEV).
Today's vulnerabilities at a glance
| Product | CVE | Severity (CVSS) | Exploitation | Fix (version) |
|---|---|---|---|---|
| nginx (HTTP/2) | CVE-2026-123007 | Major per nginx.org; F5: v4.0 9.2 / v3.1 8.1 | No reports; Rapid7 published a PoC | 1.31.9 (mainline) / 1.30.7 (stable). Workaround: disable HTTP/2 |
| nginx (HTTP/2 proxy) | CVE-2026-123633 | Medium per nginx.org; F5: v4.0 9.2 / v3.1 8.1 | No reports | 1.31.9 / 1.30.7 |
| nginx (TLS 1.3) | CVE-2026-118899 | Major per nginx.org; F5: v4.0 8.7 / v3.1 7.5 | No reports | 1.31.9 / 1.30.7 |
| nginx (mail proxy) | CVE-2026-113425 | Major per nginx.org; F5: v4.0 9.2 / v3.1 8.1 | No reports | 1.31.9 / 1.30.7 |
| nginx (resolver) | CVE-2026-123634 | Medium per nginx.org; F5: v4.0 9.2 / v3.1 8.1 | No reports | 1.31.9 / 1.30.7 |
| Ruby (strings and regexps), 7 issues | GHSA-34m4-m9fh-gqp5 and others (no CVE yet) | No CVSS in the advisory | No exploitation found; PoCs exist for some | 3.3.14 / 3.4.13 / 4.0.10. No fix for 3.2 and earlier |
| BerriAI LiteLLM | CVE-2026-40217 | 8.8 (NVD v3.1); vendor: v4.0 5.9 (Moderate) | Exploited (KEV, Nov 18) | 1.83.11 or later |
| Synology DSM / BeeStation OS | CVE-2024-10441 | 9.8 (v3.1, Synology) | Exploited (KEV, Nov 18) | DSM 7.2.2-72806-1 / 7.2.1-69057-6 / 7.2-64570-4 or later |
| Apache Axis 1.x | CVE-2026-90436 | 9.8 (v3.1 in NVD) | Exploited (KEV, Nov 18) | No fix (end of life). Migrate |
| REDCap | CVE-2026-90817 | 9.8 (v3.1 in NVD) | Exploited (KEV, Nov 18) | CVE record lists 16.0.49, 17.3.10, 17.4.4 as unaffected |
nginx CVE-2026-123007 — an HTTP/2 flow-control error that corrupts memory and may allow remote code execution
What happens. HTTP/2 has a mechanism called flow control that adjusts how much data is sent. In nginx's handling of it, crafted traffic can push a control value beyond its allowed range and corrupt heap memory. Usually only a worker process crashes, but F5 says code execution is possible where ASLR is disabled or the attacker can bypass it. Researchers at Xint found the flaw, and Rapid7 and Wiz verified it. Wiz states that even a default setup that merely serves static files over HTTPS is exploitable when HTTP/2 is enabled.
Severity. nginx.org rates it Major. F5 scores it CVSS v4.0 9.2 (Critical) and v3.1 8.1 (High), with attack complexity rated high.
Affected and fixed versions. nginx open source 1.9.5 through 1.31.8 is affected. Fixed releases are 1.31.9 (mainline) and 1.30.7 (stable). For NGINX Plus, Rapid7 lists 37.0.8.1 for the 37.0.x line and 37.3.0.1 for 37.1-37.2, and says no fix is listed for R34-R36; Plus users should check F5's advisory (K000163926). OS-packaged builds (Debian, Ubuntu, RHEL and others) may be fixed under different version numbers, so check each distribution's security notice.
Exploitation status. Rapid7 published on GitHub a PoC that achieves unauthenticated code execution against an nginx 1.31.8 Docker image with HTTP/2 and TLS enabled. It needs about 128 GB of HTTP/2 traffic, which imposes practical limits. Xint says it deliberately withheld the full steps, and Wiz says its PoC is unreleased. None of the sources reports exploitation in real attacks, but with a PoC out, updating soon is advisable.
Workaround and checks. If you cannot update immediately, turn HTTP/2 off. On 1.25.1 or later, put the line below in the affected server block; on earlier versions, remove the http2 parameter from the listen directive. Reload and verify afterward, and revert after updating.
# Check the version
nginx -v
# Disable HTTP/2 (1.25.1 or later, inside the server block)
http2 off;
# For 1.25.0 or earlier: remove http2 from listen
# Before: listen 443 ssl http2;
# After: listen 443 ssl;The other flaw, CVE-2026-123633 (HTTP/2 use-after-free), occurs when HTTP/2 traffic is proxied to a backend and worker_connections runs low. It affects 1.19.7 through 1.31.8 and is fixed in 1.31.9 / 1.30.7; Wiz built PoCs but has not released them. The same release also fixes a TLS 1.3 infinite loop (CVE-2026-118899, denial of service), a mail proxy use-after-free (CVE-2026-113425), a resolver use-after-free (CVE-2026-123634), an HTTP/3 use-after-free and more. Updating to 1.31.9 / 1.30.7 covers all of them.
For detailed verification steps, see Checking and fixing nginx CVE-2026-123007.
Official sources: nginx security advisories, NVD CVE-2026-123007, Wiz, Rapid7.
Seven Ruby vulnerabilities (nicknamed Ruby2ßhell) — reachable before authentication in Rails by default
What happens. On Nov 18, Ruby disclosed seven vulnerabilities in string case conversion and regular expressions. No CVEs are assigned yet, so they are tracked by GitHub Security Advisory IDs (GHSA). The headline one, GHSA-34m4-m9fh-gqp5, is a heap overflow in case conversion (such as upcase) where the output area is one byte short. The others include a double free and buffer overflows when compiling crafted regular expressions, and out-of-bounds reads in case-insensitive matching.
Why it is widespread, and conditions. According to Veria Labs, who analyzed it, GHSA-34m4-m9fh-gqp5 is reachable before authentication by default in Ruby on Rails and classic-style Sinatra. However, UTF-8 strings are not affected. It applies to legacy single-byte encodings such as the ISO-8859 and Windows-125x families, where converting ß to two characters (SS) exceeds the allocated space. Other frameworks and plain Rack are described as not reachable by default.
Affected and fixed versions. Ruby 3.3.13 and earlier, 3.4.0-3.4.12 and 4.0.0-4.0.9 are affected; fixed releases are 3.3.14, 3.4.13 and 4.0.10. Ruby 3.2 and earlier are end of life and will not receive these fixes. The official advisory lists no workaround and strongly recommends upgrading. Veria Labs advises users of self-hosted software that bundles Ruby (GitLab, GitHub Enterprise Server, Mastodon, OpenProject, Discourse, Chatwoot and others) to install each vendor's fixed release.
Exploitation status. No exploitation reports were found in our sources. Ruby's advisory says PoCs exist for some items, and Veria Labs plans to publish a PoC about a week after giving users time to upgrade. Attacks may increase after that, so updating before then is practical.
# Check the Ruby version
ruby -v
# Ruby version for a Bundler-managed app
bundle exec ruby -vOfficial sources: Ruby advisory, Veria Labs write-up.
Four additions to CISA KEV on Nov 18 — LiteLLM, Synology DSM, Apache Axis and REDCap
CISA added the following four entries to the KEV catalog on Nov 18, with the due dates shown. KEV lists vulnerabilities confirmed as exploited, so listing means they were actually used in attacks.
BerriAI LiteLLM CVE-2026-40217 (due Dec 2). LiteLLM is a proxy that calls many AI models in one format. Its /guardrails/test_custom_code endpoint runs user-written Python in a hand-rolled sandbox, and the sandbox can be escaped to execute arbitrary code. The vendor advisory lists affected versions as 1.81.8 up to but not including 1.83.10 and the fix as 1.83.11 or later (the advisory header says 1.83.10, but its body says 1.83.11). A proxy admin credential is required, and the vendor rates it Moderate (CVSS v4.0 5.9); NVD lists v3.1 8.8. The default Docker image runs as root, so a successful attack has a large impact. If you cannot update, block POST /guardrails/test_custom_code at the reverse proxy. Related: the LiteLLM supply-chain compromise.
Synology DSM / BeeStation OS CVE-2024-10441 (due Nov 21). A flaw in output handling in the system plugin daemon may let a remote attacker run arbitrary code. Synology rates it CVSS v3.1 9.8 (Critical). It is an old vulnerability disclosed in November 2024, yet it was added to KEV on Nov 18. Fixed versions are DSM 7.2.2-72806-1, 7.2.1-69057-6 and 7.2-64570-4 or later, and BeeStation OS 1.1-65374 or later. Synology lists no workaround. If a NAS is exposed to the internet, check whether updates have been postponed for a long time. Related: the Synology DSM SQL injection.
Apache Axis 1.x CVE-2026-90436 (due Nov 21). An old SOAP library for Java. A crafted SOAP fault message makes it load a class before authentication, which can lead to code execution if a usable class is on the application's classpath. NVD lists CVSS v3.1 9.8. Axis 1.x is end of life, all versions through 1.4 are affected, and no fix will be released. Apache recommends migrating to another SOAP engine such as Axis2. Check whether any old Java-based integrations in your internal systems or partner links use it.
REDCap CVE-2026-90817 (due Nov 21). A university-developed data collection system for clinical research, rarely used by ordinary companies. It may allow unauthenticated code execution through a public survey route, and NVD lists CVSS v3.1 9.8. An attacker needs a valid survey hash. The CVE record lists 16.0.49, 17.3.10 and 17.4.4 as unaffected; update to one of these or later and check the vendor's guidance. If you use it, check the operator's notice.
Official sources: CISA KEV catalog, LiteLLM advisory, Synology SA-24-20, Apache announcement.
Checklist for non-IT staff: what to do today
- Ask your vendors whether any server uses nginx and whether it is 1.31.9 / 1.30.7 or later. If it cannot be updated, ask them to disable HTTP/2 temporarily (http2 off;)
- If you rent a web server or cloud hosting, check the provider's notice about their response
- If you have a business system built on Ruby on Rails, ask the developer whether Ruby is 3.3.14 / 3.4.13 / 4.0.10 or later. If it is 3.2 or earlier, discuss a migration plan
- If you expose a Synology NAS to the internet, update DSM. If you don't use one, record it as not applicable
- If you run LiteLLM in-house, update to 1.83.11 or later and check that the admin interface is not exposed externally
- Ask your IT contact whether any old Java-based SOAP integration (Apache Axis 1.x) remains
- If you use none of these, record "not applicable" and you are done
Related articles
Preparation against vulnerabilities is covered in Vulnerability assessment cost and how to choose. For the previous day, see Nov 18 digest (Java4Shell and more).
Sources
- nginx security advisories: https://nginx.org/en/security_advisories.html
- NVD CVE-2026-123007: https://nvd.nist.gov/vuln/detail/CVE-2026-123007
- NVD CVE-2026-123633: https://nvd.nist.gov/vuln/detail/CVE-2026-123633
- NVD CVE-2026-118899: https://nvd.nist.gov/vuln/detail/CVE-2026-118899
- NVD CVE-2026-113425: https://nvd.nist.gov/vuln/detail/CVE-2026-113425
- NVD CVE-2026-123634: https://nvd.nist.gov/vuln/detail/CVE-2026-123634
- Wiz (nginx HTTP/2): https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
- Rapid7 (CVE-2026-123007): https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/
- Xint (nginx2root): https://xint.io/blog/nginx2root-remote-code-execution
- Ruby advisory (Nov 18, 2026): https://www.ruby-lang.org/en/news/2026/11/18/multiple-vulnerabilities-in-regexp-and-string/
- Veria Labs (Ruby2ßhell): https://verialabs.com/ruby2shell/
- CISA KEV catalog (Nov 18 additions checked in the JSON feed): https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- LiteLLM GHSA-wxxx-gvqv-xp7p: https://github.com/BerriAI/litellm/security/advisories/GHSA-wxxx-gvqv-xp7p
- NVD CVE-2026-40217: https://nvd.nist.gov/vuln/detail/CVE-2026-40217
- Synology SA-24-20: https://www.synology.com/en-global/support/security/Synology_SA_24_20
- NVD CVE-2024-10441: https://nvd.nist.gov/vuln/detail/CVE-2024-10441
- Apache Axis 1.x announcement (CVE-2026-90436): https://lists.apache.org/thread/8slf0j9gz35z56t0glt5h0ncwlbn4bdz
- NVD CVE-2026-90436: https://nvd.nist.gov/vuln/detail/CVE-2026-90436
- NVD CVE-2026-90817: https://nvd.nist.gov/vuln/detail/CVE-2026-90817
FAQ
Is every nginx server in danger?
No. CVE-2026-123007 affects nginx with HTTP/2 enabled; without HTTP/2 it is not affected. However, many HTTPS sites have HTTP/2 on. Rapid7's PoC needs about 128 GB of traffic and the sources we checked report no real-world exploitation, but updating is the safe course.
What if I cannot update nginx right away?
You can disable HTTP/2. On 1.25.1 or later, add http2 off; to the server block; on earlier versions, remove the http2 parameter from listen. Reload and verify the site. Pages may load slightly slower without HTTP/2. Revert after updating.
Am I safe from the Ruby flaws if I use UTF-8?
GHSA-34m4-m9fh-gqp5 (Ruby2ßhell) is described as not affecting UTF-8 strings. However, the regular-expression issues among the seven may be affected under other conditions. Updating Ruby (3.3.14 / 3.4.13 / 4.0.10) is the most reliable step. If you use 3.2 or earlier, no fix will come, so consider moving to a newer version.
Do I still need to act on an old Synology vulnerability that just entered KEV?
Yes. CVE-2024-10441 had a fix in 2024 but was added to KEV on Nov 18 because exploitation was confirmed. If DSM is older than 7.2.2-72806-1 / 7.2.1-69057-6 / 7.2-64570-4, update it. Synology lists no workaround, so updating is the only remedy.
Does updating fix Apache Axis 1.x?
No. Axis 1.x is end of life, all versions through 1.4 are affected and no fix will be released. Apache recommends migrating to another SOAP engine such as Axis2. Ask your system developer whether you use it.
株式会社オブライト
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