Monthly data · November 2026
New CVEs in end-of-life open source: November 2026
Between 1 October to 14 November 2026, 63 new CVEs affected the final release of an open-source line that no longer gets upstream fixes, and 42 were rated Critical or High. The lines hit most were PostgreSQL 11 to 13 (40), Kafka 3.9 and 4.0 (11), Node.js 18 and 20 (10). Every CVE below links to its vendor advisory and to NVD.
Window: 1 October to 14 November 2026. Data pulled and checked 14 November 2026 from each project's CVE record and NVD. First edition; the next one covers CVEs published after 14 November.
Summary by technology
63 CVEs, 3 Critical and 39 High, across four technologies. Spring, .NET and ZooKeeper had none in the window. The last column links the end-of-life page for the line.
| Product and EOL lines | CVEs in window | Critical / High | Upstream fix shipped only in | Version page |
|---|---|---|---|---|
| PostgreSQL 11 to 13 | 40 | 0 / 31 | 18.7, 17.12, 16.16, 15.20, 14.25 | PostgreSQL 13 |
| Kafka 3.9 and 4.0 | 11 | 3 / 3 | 4.2.2, 4.3.2, 4.4.0 | Kafka 3.9 |
| Node.js 18 and 20 | 10 | 0 / 4 | 22.23.5, 24.22.3, 26.13.1 | Node.js 20 |
| Tomcat 7 and 8.5 | 2 | 0 / 1 | 11.0.27, 10.1.61, 9.0.123 | Tomcat 8.5 |
| Spring Boot 2.7 and Framework 5.3 | 0 | 0 / 0 | n/a | Spring Boot 2.7 |
| .NET 6, 8 and 9 | 0 | 0 / 0 | n/a (fixed in 8.0.34 and 9.0.23) | .NET 8 |
| ZooKeeper 3.4 to 3.7 | 0 | 0 / 0 | n/a | ZooKeeper |
Critical is CVSS 9.0 to 10.0 and High 7.0 to 8.9, base scores from NVD. "Upstream fix shipped only in" lists the supported lines that received a fix; none of these CVEs has an upstream fix on the ended lines. Browse the full list in the CVE directory or the quarterly open source CVE report.
Node.js 18 and 20
The 11 November 2026 Node.js security release produced 10 CVEs whose affected range includes the last Node.js 18 and 20 releases (18.20.8 and 20.20.2): 0 Critical and 4 High. Fixes shipped in 22.23.5, 24.22.3 and 26.13.1, so nothing fixes them on 18 or 20.
| CVE | CVSS | Published | Issue | Fixed in | Advisory |
|---|---|---|---|---|---|
| CVE-2026-123864 | 8.1 High | 11 Nov | Node.js is vulnerable to cross-connection memory disclosure via TLS write re-entrancy in the HTTPS request parser | 22.23.5, 24.22.3, 26.13.1 (none for 18 or 20) | nodejs.org |
| CVE-2026-123872 | 8.1 High | 11 Nov | Node.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change | 22.23.5, 24.22.3, 26.13.1 (none for 18 or 20) | nodejs.org |
| CVE-2026-123865 | 7.5 High | 11 Nov | Node.js is vulnerable to an HTTP/2 memory and file-descriptor leak via a protocol error during session shutdown | 22.23.5, 24.22.3, 26.13.1 (none for 18 or 20) | nodejs.org |
| CVE-2026-123866 | 7.5 High | 11 Nov | Node.js is vulnerable to HTTP/2 response memory disclosure via a use-after-free during stream teardown | 22.23.5, 24.22.3, 26.13.1 (none for 18 or 20) | nodejs.org |
| CVE-2026-123877 | 6.8 Medium | 11 Nov | Node.js is vulnerable to a certificate validation bypass in https.Agent via cross-policy TLS session reuse | 22.23.5, 24.22.3, 26.13.1 (none for 18 or 20) | nodejs.org |
| CVE-2026-123871 | 6.2 Medium | 11 Nov | Node.js is vulnerable to proxy credential disclosure via ERR_PROXY_INVALID_CONFIG error messages | 22.23.5, 24.22.3, 26.13.1 (none for 18 or 20) | nodejs.org |
| CVE-2026-123875 | 5.9 Medium | 11 Nov | Node.js is vulnerable to an HTTP/2 denial of service via a NULL pointer dereference when a respondWithFile() download is cancelled | 22.23.5, 24.22.3, 26.13.1 (none for 18 or 20) | nodejs.org |
| CVE-2026-123867 | 4.2 Medium | 11 Nov | Node.js is vulnerable to a per-host mTLS authorization bypass via a CA-only SNI context failing open to the default CA | 22.23.5, 24.22.3, 26.13.1 (none for 18 or 20) | nodejs.org |
| CVE-2026-123862 | 2.9 Low | 11 Nov | Node.js is vulnerable to a zlib denial of service via a stream destroy during a pending params() call | 22.23.5, 24.22.3, 26.13.1 (none for 18 or 20) | nodejs.org |
| CVE-2026-123829 | 2.5 Low | 11 Nov | Node.js is vulnerable to Permission Model file-name disclosure via recursive fs.watch | 22.23.5, 24.22.3, 26.13.1 (none for 18 or 20) | nodejs.org |
Node.js 18 ended on 30 April 2025 and Node.js 20 on 30 April 2026. The advisory range starts at 0.0.0, so it covers every earlier line too. Five more CVEs in the same release affect only 24 and later, and are left out.
Check your line: Node.js 18 end of life, Node.js 20 end of life. Node.js CVEs by version lists every CVE by version.
Keep it patched: Node.js extended support for 18 and 20.
Spring Boot 2.7 and Spring Framework 5.3
No new CVEs in the Spring Boot, Spring Framework or Spring Security projects were published in this window, so none fell on Spring Boot 2.7 or Spring Framework 5.3. Those lines are still past their open-source end dates, so the next advisory will land on them.
Check your line: Spring Boot 2.7 end of life, Spring Framework 5.3 end of life. Spring Framework CVEs by version lists every CVE by version.
Keep it patched: Spring Boot 2.x and Spring Framework 5 extended support.
Apache Tomcat 8.5 and 7
2 CVEs published on 20 October 2026 name Tomcat 8.5.100 and 7.0.109, the final releases of those lines, in their affected range: 0 Critical and 1 High. Apache ships the fixes in 11.0.27, 10.1.61 and 9.0.123 only.
| CVE | CVSS | Published | Issue | Fixed in | Advisory |
|---|---|---|---|---|---|
| CVE-2026-101296 | 8.1 High | 20 Oct | JNDIRealm bind credential validation fails open for non-GSSAPI SASL mechanisms | 11.0.27, 10.1.61, 9.0.123 (none for 7 or 8.5) | lists.apache.org |
| CVE-2026-74049 | 6.1 Medium | 20 Oct | Jasper JSTL <c:redirect> plug-in implementation omits page abort (SKIP_PAGE) | 11.0.27, 10.1.61, 9.0.123 (none for 7 or 8.5) | lists.apache.org |
Tomcat 9.0 is supported until 31 March 2027, so it gets these fixes today. The Tomcat 10.0 line, which also ended, is not in either advisory's range. Six more Tomcat CVEs published the same day affect only 9.0 and later.
Check your line: Tomcat 8.5 end of life, Tomcat 7 end of life
Keep it patched: Tomcat extended support for 8.5 and 7.
.NET 6, 8 and 9
No .NET CVE published in this window is left unfixed on an ended line. .NET 8 and .NET 9 reached end of support on 10 November 2026; the CVE Microsoft published that day for both lines (CVE-2026-109475) is fixed in 8.0.34 and 9.0.23. No Microsoft record in the window names .NET 6.
Check your line: .NET 8 end of life, .NET 9 end of life
Keep it patched: .NET 8 extended support.
PostgreSQL 11 to 13
The PostgreSQL project published 40 CVEs on 12 November 2026 whose affected range runs from the first release up to before 14.25, which includes the final releases of PostgreSQL 11, 12 and 13 (11.22, 12.22 and 13.23): 0 Critical and 31 High. Fixes shipped in 18.7, 17.12, 16.16, 15.20 and 14.25.
| CVE | CVSS | Published | Issue | Fixed in | Advisory |
|---|---|---|---|---|---|
| CVE-2026-116304 | 8.8 High | 12 Nov | PostgreSQL parallel RECORD typmod use-after-free executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116306 | 8.8 High | 12 Nov | PostgreSQL composite-type change during field assignment executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116307 | 8.8 High | 12 Nov | PostgreSQL plperl prepared-query use-after-free executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116309 | 8.8 High | 12 Nov | PostgreSQL plperl blessed-reference type confusion may execute arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116314 | 8.8 High | 12 Nov | PostgreSQL pg_restore executes arbitrary code due to missing non-plain archive validation | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116315 | 8.8 High | 12 Nov | PostgreSQL tsvector_delete() heap buffer overflow executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116316 | 8.8 High | 12 Nov | PostgreSQL security-restricted operations can create types in pg_temp, which later queries of the session find | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116317 | 8.8 High | 12 Nov | PostgreSQL ts_rank_cd() heap buffer overflow may execute arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116319 | 8.8 High | 12 Nov | PostgreSQL plperl reentrant return_next() use-after-free executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116320 | 8.8 High | 12 Nov | PostgreSQL plperl array and hash conversion use-after-free executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116323 | 8.8 High | 12 Nov | PostgreSQL pltcl reentrant result conversion use-after-free executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116326 | 8.8 High | 12 Nov | PostgreSQL plperl tied-object exceptions follow stale sigjmp_buf | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116330 | 8.8 High | 12 Nov | PostgreSQL pg_dump tar restore.sql fails to block psql command injection | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116331 | 8.8 High | 12 Nov | PostgreSQL min/max aggregate type confusion executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116332 | 8.8 High | 12 Nov | PostgreSQL portal setup use-after-free executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116335 | 8.8 High | 12 Nov | PostgreSQL commutator or negator result-type confusion executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116336 | 8.8 High | 12 Nov | PostgreSQL REINDEX CONCURRENTLY does not block DROP INDEX during index functions | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-120139 | 8.8 High | 12 Nov | PostgreSQL tuple-size integer wraparound executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-120141 | 8.8 High | 12 Nov | PostgreSQL materialized set-returning function type confusion executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-120143 | 8.8 High | 12 Nov | PostgreSQL transition-table cursor use-after-free executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-120145 | 8.8 High | 12 Nov | PostgreSQL logical replication can write to subscriber system catalogs, executing arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-120147 | 8.8 High | 12 Nov | PostgreSQL dblink reentrant disconnect use-after-free executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-120149 | 8.8 High | 12 Nov | PostgreSQL FDW batch-insert mismatch executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-120150 | 8.8 High | 12 Nov | PostgreSQL expanded-record domain-check use-after-free executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-120151 | 8.8 High | 12 Nov | PostgreSQL plpgsql record-field type confusion executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-18447 | 8.8 High | 12 Nov | PostgreSQL output parameter type confusion executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-6460 | 8.8 High | 12 Nov | PostgreSQL type confusion after ALTER ... SET DATA TYPE executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-120148 | 8.1 High | 12 Nov | PostgreSQL extended-statistics pseudo-type confusion executes arbitrary code | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-14661 | 8.1 High | 12 Nov | PostgreSQL dblink and subscriptions can append to arbitrary files | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-120153 | 7.2 High | 12 Nov | PostgreSQL extension-script substitutions allow SQL injection through object names | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-6467 | 7.2 High | 12 Nov | PostgreSQL extension script schema mishandling executes arbitrary SQL | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116311 | 5.4 Medium | 12 Nov | PostgreSQL DROP OWNED can remove restrictive row security policies from non-owned tables | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-16237 | 5.4 Medium | 12 Nov | PostgreSQL INSERT ... ON CONFLICT can read or modify rows despite auto-updatable view WHERE condition | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116308 | 4.3 Medium | 12 Nov | PostgreSQL dict_int reads beyond zero-length tokens | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116321 | 4.3 Medium | 12 Nov | PostgreSQL unterminated name value discloses server memory | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116327 | 4.3 Medium | 12 Nov | PostgreSQL security_barrier analysis can expose hidden values through indirect expressions | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-120146 | 4.3 Medium | 12 Nov | PostgreSQL REASSIGN OWNED bypasses role SET and CREATEDB checks | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-120154 | 4.3 Medium | 12 Nov | PostgreSQL INSERT ... ON CONFLICT can read rows despite row security policies | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-16240 | 3.7 Low | 12 Nov | PostgreSQL pg_basebackup can use backup manifest content as a format string | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
| CVE-2026-116303 | 3.1 Low | 12 Nov | PostgreSQL foreign key and JSON conversions bypass EXECUTE privilege on cast functions | 18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13) | postgresql.org |
PostgreSQL 13 ended on 13 November 2025, 12 on 21 November 2024 and 11 on 9 November 2023. PostgreSQL 14 reached end of life on the day the CVEs were published, 12 November 2026, and its final release 14.25 carries the fixes.
Check your line: PostgreSQL 13 end of life, PostgreSQL 12 end of life. PostgreSQL CVEs by version lists every CVE by version.
Keep it patched: PostgreSQL 13 and 14 extended support.
Kafka and ZooKeeper
Apache published 11 Kafka CVEs on 28 October 2026 that name Kafka 3.9.2 and 4.0.2, the final releases of those lines, in their affected range: 3 Critical and 3 High. Fixes ship in 4.2.2, 4.3.2 and 4.4.0 (CVE-2026-111073: 4.3.1). Five ZooKeeper CVEs published on 4 November 2026 affect 3.8 and 3.9 only, so no ended ZooKeeper line is hit.
| CVE | CVSS | Published | Issue | Fixed in | Advisory |
|---|---|---|---|---|---|
| CVE-2026-111108 | 9.1 Critical | 28 Oct | Broker OutOfMemoryError via array allocation amplification in code-generated protocol readers | 4.2.2, 4.3.2, 4.4.0 | kafka.apache.org |
| CVE-2026-111115 | 9.1 Critical | 28 Oct | Broker OutOfMemoryError via tagged-field allocation amplification in flexible protocol request parsing | 4.2.2, 4.3.2, 4.4.0 | kafka.apache.org |
| CVE-2026-111496 | 9.1 Critical | 28 Oct | Kafka Streams StreamThread hang from integer overflow in stream-time punctuation | 4.2.2, 4.3.2, 4.4.0 | kafka.apache.org |
| CVE-2026-115644 | 8.8 High | 28 Oct | Connect Admin REST API Authentication Bypass via Unapplied REST Extensions | 4.2.2, 4.3.2, 4.4.0 | kafka.apache.org |
| CVE-2026-116593 | 8.1 High | 28 Oct | Kafka Connect configuration provider values exposed via validation REST API endpoint | 4.2.2, 4.3.2, 4.4.0 | kafka.apache.org |
| CVE-2026-111551 | 7.5 High | 28 Oct | Denial of service in Kafka Streams and client deserializers via unbounded memory allocation | 4.2.2, 4.3.2, 4.4.0 | kafka.apache.org |
| CVE-2026-111073 | 6.5 Medium | 28 Oct | PushTelemetry (KIP-714) metrics payloads are decompressed without a size limit, allowing a broker out-of-memory denial of service | 4.2.2, 4.3.1, 4.4.0 | kafka.apache.org |
| CVE-2026-112375 | 6.5 Medium | 28 Oct | Unauthorized principal can read arbitrary broker files via IncrementalAlterConfigs | 4.2.2, 4.3.2, 4.4.0 | kafka.apache.org |
| CVE-2026-114349 | 6.5 Medium | 28 Oct | Denial of service via unbounded memory allocation when decoding compressed record batches | 4.2.2, 4.3.2, 4.4.0 | kafka.apache.org |
| CVE-2026-83525 | 6.5 Medium | 28 Oct | Incorrect boolean operator in FetchSnapshot RPC handler allows authenticated network clients to crash the KRaft controller via a malformed request. | 4.2.2, 4.3.2 | kafka.apache.org |
| CVE-2026-110952 | 5.9 Medium | 28 Oct | Broker does not enforce JWT issuer and audience validation for SASL/OAUTHBEARER by default | 4.4.0 | kafka.apache.org |
Kafka 3.9 and 4.0 both ended on 3 July 2026 on endoflife.date. Apache's notice for CVE-2026-83525 calls 4.1.x and earlier unsupported branches and tells those users to move to 4.2.2 or later. One more Kafka CVE published that day (CVE-2026-110985) affects 4.1 and later only.
Check your line: Kafka 3.9 end of life, every Kafka version. Kafka CVEs by version lists every CVE by version.
Keep it patched: Kafka and ZooKeeper extended support.
How fast are EOL CVEs patched?
Upstream projects do not ship fixes for end-of-life lines, as the tables above show. OSSeva Patch ships Critical (CVSS 9.0+) fixes within 48 hours and High within 7 days. This round-up does not report OSSeva build dates for these CVEs: none of the 63 is in the OSSeva CVE directory yet, so the page makes no patched-build claim for any of them. Other providers' windows are not stated here because this page has not checked them.
How we counted
- Window and date. CVEs with a publication date from 1 October to 14 November 2026. Data pulled on 14 November 2026.
- Source. The CVE record published by each project's own CVE numbering authority (Apache for Tomcat, Kafka and ZooKeeper, the OpenJS Foundation for Node.js, the PostgreSQL project for PostgreSQL), read from the CVE Services API (cveawg.mitre.org). CVSS base scores come from NVD (nvd.nist.gov). Every row links the vendor advisory and NVD.
- Match. A CVE is counted for a line when the record's affected range includes that line's final release: Node.js 18.20.8 and 20.20.2, Tomcat 7.0.109 and 8.5.100, PostgreSQL 11.22, 12.22 and 13.23, Kafka 3.9.2 and 4.0.2. Where an advisory's range starts at the first release, as Node.js and PostgreSQL do, the ended lines count as affected.
- End-of-life dates. From each project's lifecycle policy and endoflife.date, checked on 14 November 2026. A line counts only if it had ended before the CVE was published, which is why PostgreSQL 14 (ended 12 November, fixed in its final release 14.25) and .NET 8 and 9 (fixed in their final releases) are not counted.
- What is not counted. CVEs in third-party libraries or add-ons (for example PostgreSQL Anonymizer, pgAdmin, undici or Node.js drivers), and CVEs whose range excludes every ended line. The OSSeva CVE directory is not the data source: it is a curated list and holds two records dated in this window, neither on a line covered here.
What are the limits of this page?
- An advisory's affected range is the project's statement. Where it begins at the first release, older lines are covered by the range, but the project has not tested every ended line.
- A CVE count is not a risk score. A CVE you do not expose matters less than one on your edge.
- OSSeva sells extended support for these technologies. Read the framing with that in mind and check each row against the linked advisory.
Do end-of-life versions get CVE fixes?
Not from the upstream project. In this window Node.js, Tomcat, PostgreSQL and Kafka each shipped fixes only in lines that were still supported, while the advisories' affected ranges also covered the ended lines. A third-party provider can backport the fixes; OSSeva does this for the technologies in this round-up.
How do I check whether my version is affected?
Find your exact version in the advisory linked from each row, then compare it with the affected range and the fixed-in versions. The CVE directory lists affected versions for the CVEs it covers, and the EOL tracker shows whether your line still gets upstream fixes.
How often is this updated?
Monthly. The next edition covers CVEs published after 14 November 2026, and the page's modified date moves only when the data does.
Get a quote
Running an end-of-life line from this round-up?
A 15-minute call establishes which of your versions still receive fixes and which CVEs above apply to them.
Prefer to talk or read more first?