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.

CVEs in end-of-life release lines, 1 October to 14 November 2026
Product and EOL linesCVEs in windowCritical / HighUpstream fix shipped only inVersion page
PostgreSQL 11 to 13400 / 3118.7, 17.12, 16.16, 15.20, 14.25PostgreSQL 13
Kafka 3.9 and 4.0113 / 34.2.2, 4.3.2, 4.4.0Kafka 3.9
Node.js 18 and 20100 / 422.23.5, 24.22.3, 26.13.1Node.js 20
Tomcat 7 and 8.520 / 111.0.27, 10.1.61, 9.0.123Tomcat 8.5
Spring Boot 2.7 and Framework 5.300 / 0n/aSpring Boot 2.7
.NET 6, 8 and 900 / 0n/a (fixed in 8.0.34 and 9.0.23).NET 8
ZooKeeper 3.4 to 3.700 / 0n/aZooKeeper

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.

Node.js 18 and 20: CVEs published in the window
CVECVSSPublishedIssueFixed inAdvisory
CVE-2026-1238648.1 High11 NovNode.js is vulnerable to cross-connection memory disclosure via TLS write re-entrancy in the HTTPS request parser22.23.5, 24.22.3, 26.13.1 (none for 18 or 20)nodejs.org
CVE-2026-1238728.1 High11 NovNode.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change22.23.5, 24.22.3, 26.13.1 (none for 18 or 20)nodejs.org
CVE-2026-1238657.5 High11 NovNode.js is vulnerable to an HTTP/2 memory and file-descriptor leak via a protocol error during session shutdown22.23.5, 24.22.3, 26.13.1 (none for 18 or 20)nodejs.org
CVE-2026-1238667.5 High11 NovNode.js is vulnerable to HTTP/2 response memory disclosure via a use-after-free during stream teardown22.23.5, 24.22.3, 26.13.1 (none for 18 or 20)nodejs.org
CVE-2026-1238776.8 Medium11 NovNode.js is vulnerable to a certificate validation bypass in https.Agent via cross-policy TLS session reuse22.23.5, 24.22.3, 26.13.1 (none for 18 or 20)nodejs.org
CVE-2026-1238716.2 Medium11 NovNode.js is vulnerable to proxy credential disclosure via ERR_PROXY_INVALID_CONFIG error messages22.23.5, 24.22.3, 26.13.1 (none for 18 or 20)nodejs.org
CVE-2026-1238755.9 Medium11 NovNode.js is vulnerable to an HTTP/2 denial of service via a NULL pointer dereference when a respondWithFile() download is cancelled22.23.5, 24.22.3, 26.13.1 (none for 18 or 20)nodejs.org
CVE-2026-1238674.2 Medium11 NovNode.js is vulnerable to a per-host mTLS authorization bypass via a CA-only SNI context failing open to the default CA22.23.5, 24.22.3, 26.13.1 (none for 18 or 20)nodejs.org
CVE-2026-1238622.9 Low11 NovNode.js is vulnerable to a zlib denial of service via a stream destroy during a pending params() call22.23.5, 24.22.3, 26.13.1 (none for 18 or 20)nodejs.org
CVE-2026-1238292.5 Low11 NovNode.js is vulnerable to Permission Model file-name disclosure via recursive fs.watch22.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.

Apache Tomcat 8.5 and 7: CVEs published in the window
CVECVSSPublishedIssueFixed inAdvisory
CVE-2026-1012968.1 High20 OctJNDIRealm bind credential validation fails open for non-GSSAPI SASL mechanisms11.0.27, 10.1.61, 9.0.123 (none for 7 or 8.5)lists.apache.org
CVE-2026-740496.1 Medium20 OctJasper 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.

PostgreSQL 11 to 13: CVEs published in the window
CVECVSSPublishedIssueFixed inAdvisory
CVE-2026-1163048.8 High12 NovPostgreSQL parallel RECORD typmod use-after-free executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163068.8 High12 NovPostgreSQL composite-type change during field assignment executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163078.8 High12 NovPostgreSQL plperl prepared-query use-after-free executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163098.8 High12 NovPostgreSQL plperl blessed-reference type confusion may execute arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163148.8 High12 NovPostgreSQL pg_restore executes arbitrary code due to missing non-plain archive validation18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163158.8 High12 NovPostgreSQL tsvector_delete() heap buffer overflow executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163168.8 High12 NovPostgreSQL security-restricted operations can create types in pg_temp, which later queries of the session find18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163178.8 High12 NovPostgreSQL ts_rank_cd() heap buffer overflow may execute arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163198.8 High12 NovPostgreSQL plperl reentrant return_next() use-after-free executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163208.8 High12 NovPostgreSQL plperl array and hash conversion use-after-free executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163238.8 High12 NovPostgreSQL pltcl reentrant result conversion use-after-free executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163268.8 High12 NovPostgreSQL plperl tied-object exceptions follow stale sigjmp_buf18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163308.8 High12 NovPostgreSQL pg_dump tar restore.sql fails to block psql command injection18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163318.8 High12 NovPostgreSQL min/max aggregate type confusion executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163328.8 High12 NovPostgreSQL portal setup use-after-free executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163358.8 High12 NovPostgreSQL commutator or negator result-type confusion executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163368.8 High12 NovPostgreSQL REINDEX CONCURRENTLY does not block DROP INDEX during index functions18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1201398.8 High12 NovPostgreSQL tuple-size integer wraparound executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1201418.8 High12 NovPostgreSQL materialized set-returning function type confusion executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1201438.8 High12 NovPostgreSQL transition-table cursor use-after-free executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1201458.8 High12 NovPostgreSQL logical replication can write to subscriber system catalogs, executing arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1201478.8 High12 NovPostgreSQL dblink reentrant disconnect use-after-free executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1201498.8 High12 NovPostgreSQL FDW batch-insert mismatch executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1201508.8 High12 NovPostgreSQL expanded-record domain-check use-after-free executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1201518.8 High12 NovPostgreSQL plpgsql record-field type confusion executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-184478.8 High12 NovPostgreSQL output parameter type confusion executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-64608.8 High12 NovPostgreSQL type confusion after ALTER ... SET DATA TYPE executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1201488.1 High12 NovPostgreSQL extended-statistics pseudo-type confusion executes arbitrary code18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-146618.1 High12 NovPostgreSQL dblink and subscriptions can append to arbitrary files18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1201537.2 High12 NovPostgreSQL extension-script substitutions allow SQL injection through object names18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-64677.2 High12 NovPostgreSQL extension script schema mishandling executes arbitrary SQL18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163115.4 Medium12 NovPostgreSQL DROP OWNED can remove restrictive row security policies from non-owned tables18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-162375.4 Medium12 NovPostgreSQL INSERT ... ON CONFLICT can read or modify rows despite auto-updatable view WHERE condition18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163084.3 Medium12 NovPostgreSQL dict_int reads beyond zero-length tokens18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163214.3 Medium12 NovPostgreSQL unterminated name value discloses server memory18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163274.3 Medium12 NovPostgreSQL security_barrier analysis can expose hidden values through indirect expressions18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1201464.3 Medium12 NovPostgreSQL REASSIGN OWNED bypasses role SET and CREATEDB checks18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1201544.3 Medium12 NovPostgreSQL INSERT ... ON CONFLICT can read rows despite row security policies18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-162403.7 Low12 NovPostgreSQL pg_basebackup can use backup manifest content as a format string18.7, 17.12, 16.16, 15.20, 14.25 (none for 11 to 13)postgresql.org
CVE-2026-1163033.1 Low12 NovPostgreSQL foreign key and JSON conversions bypass EXECUTE privilege on cast functions18.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.

Kafka and ZooKeeper: CVEs published in the window
CVECVSSPublishedIssueFixed inAdvisory
CVE-2026-1111089.1 Critical28 OctBroker OutOfMemoryError via array allocation amplification in code-generated protocol readers4.2.2, 4.3.2, 4.4.0kafka.apache.org
CVE-2026-1111159.1 Critical28 OctBroker OutOfMemoryError via tagged-field allocation amplification in flexible protocol request parsing4.2.2, 4.3.2, 4.4.0kafka.apache.org
CVE-2026-1114969.1 Critical28 OctKafka Streams StreamThread hang from integer overflow in stream-time punctuation4.2.2, 4.3.2, 4.4.0kafka.apache.org
CVE-2026-1156448.8 High28 OctConnect Admin REST API Authentication Bypass via Unapplied REST Extensions4.2.2, 4.3.2, 4.4.0kafka.apache.org
CVE-2026-1165938.1 High28 OctKafka Connect configuration provider values exposed via validation REST API endpoint4.2.2, 4.3.2, 4.4.0kafka.apache.org
CVE-2026-1115517.5 High28 OctDenial of service in Kafka Streams and client deserializers via unbounded memory allocation4.2.2, 4.3.2, 4.4.0kafka.apache.org
CVE-2026-1110736.5 Medium28 OctPushTelemetry (KIP-714) metrics payloads are decompressed without a size limit, allowing a broker out-of-memory denial of service4.2.2, 4.3.1, 4.4.0kafka.apache.org
CVE-2026-1123756.5 Medium28 OctUnauthorized principal can read arbitrary broker files via IncrementalAlterConfigs4.2.2, 4.3.2, 4.4.0kafka.apache.org
CVE-2026-1143496.5 Medium28 OctDenial of service via unbounded memory allocation when decoding compressed record batches4.2.2, 4.3.2, 4.4.0kafka.apache.org
CVE-2026-835256.5 Medium28 OctIncorrect boolean operator in FetchSnapshot RPC handler allows authenticated network clients to crash the KRaft controller via a malformed request.4.2.2, 4.3.2kafka.apache.org
CVE-2026-1109525.9 Medium28 OctBroker does not enforce JWT issuer and audience validation for SASL/OAUTHBEARER by default4.4.0kafka.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

  1. Window and date. CVEs with a publication date from 1 October to 14 November 2026. Data pulled on 14 November 2026.
  2. 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.
  3. 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.
  4. 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.
  5. 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.

Questions

Frequently asked questions

Book a 15-minute call

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.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call