Security Intelligence · Updated 2026-09-06
Exploited & Unpatchable
Actively exploited vulnerabilities affecting software versions that have passed end-of-life and are not expected to receive a fix. This list is the intersection of two public facts that normally live apart: CISA's Known Exploited Vulnerabilities catalog (what attackers are actually using) and verified end-of-life data (which versions have run out of patches). When a version appears in both, the vendor's fix ships only to supported releases and none is expected for the end-of-life one. Every entry below is verified by hand against the vendor's own advisory.
23Verified entries
18Products
100%Primary-source verified
DailyRadar review
We deliberately publish fewer records rather than publish uncertain ones: our 2026 verification sweep checked ~98 candidate (CVE × EOL-version) pairs line-by-line against primary vendor advisories and rejected roughly 88% — most often because the vendor had quietly backported a fix to the "dead" version. What survives is the residue that no patch will ever reach. Verified against CISA KEV, vendor advisories, and lifecycle data.
The question other vulnerability feeds don't answer
KEV tells you a flaw is being exploited. CVSS tells you how severe it is. Neither tells you whether the version you are running will ever be fixed. Exploited + past end-of-life = a remediation problem no patch will close — the only paths are upgrade, replace, or an accepted, documented risk. This is the list where that is already the case.
What qualifies
A CVE on CISA's Known Exploited Vulnerabilities catalog that affects one or more product versions past their vendor end-of-life date, where the vendor's fix ships only in supported versions and no update is expected for the end-of-life line. If a vendor later backports a fix to an end-of-life version, that entry is removed. Conservative by design — an entry is listed only when the vendor's affected-versions and fixed-versions lists both confirm the gap.
Three scores, three questions — and they disagree
Each entry carries three signals, and they measure different things.
CVSS asks how bad it would be if exploited.
CISA KEV confirms it
is being exploited.
EPSS — from
FIRST.org — estimates the probability of exploitation in the wild over the next 30 days.
They routinely disagree, and the disagreement is informative rather than a flaw. A vulnerability can sit on CISA KEV, meaning exploitation is confirmed, while carrying a low EPSS probability: EPSS predicts the near-term
volume of exploitation activity, so a flaw exploited in targeted attacks rather than mass scanning scores low even though it is unambiguously being used. On this list, FortiOS CVE-2025-68686 is exactly that case. The reverse also appears — high severity paired with a modest probability, as with TeamCity CVE-2026-63077 at CVSS 9.8.
Read them together: KEV for what is happening, EPSS for what is likely next, CVSS for the cost if it lands — and end-of-life status for whether a fix is ever coming.
Worked examples of all three disagreeing → EPSS values are model output, refreshed daily and shown with the date they were scored; unlike every other figure here they are not human-verified, and they never affect whether an entry appears on this list.
Free security intelligence feed
Use it in vulnerability management, dashboards, security research, and AI agents. Attribution to endoflife.ai. Want version-level lifecycle + risk intelligence for any product, or to license this feed for a product you sell?
See the API → ·
Commercial & data licensing →
CVSS 8.8
CISA KEV
EPSS 1.6% (30d)
Missing authentication for critical function in the web management interface: under specific conditions, unauthenticated remote requests targeting administrative functions trigger backend actions before access validation completes, letting an unauthenticated remote attacker modify certain system configurations. Chains with CVE-2026-82078 (unsafe dynamic class loading) into pre-auth remote code execution. (Missing authentication for critical function (CWE-306))
End-of-life versions affected — no fix will come
23 and earlier
Fixed only in
24 (Emergency Patch Release 3), 25 (Emergency Patch Release 3), 26 (Emergency Patch Release 3)
Why it stays unpatched
Same vendor decision as CVE-2026-82078, with which this chains: PaperCut publishes no end-of-life calendar, and its September 2026 advisory states the path for everything before v24 is upgrade - Emergency Patch Release 3 shipped for v24/v25/v26 only. The two CVEs together are the exploited-in-the-wild chain (unauthenticated configuration modification feeding unsafe class loading); a v23-or-earlier server exposed to the internet has no patch coming for either half. CISA's required action includes discontinuing use where mitigations are unavailable.
CVSS 9.4
CISA KEV
EPSS 1.7% (30d)
Unsafe dynamic class loading in the database connection utilities: the application instantiates database driver classes from configurable driver names without an allowlist, letting an attacker who can modify configuration execute arbitrary Java bytecode on the classpath under the PaperCut server process. Chains with CVE-2026-81578 (unauthenticated configuration modification) into pre-auth remote code execution. (Unsafe reflection / dynamic class loading (chained to pre-auth RCE))
End-of-life versions affected — no fix will come
23 and earlier
Fixed only in
24 (Emergency Patch Release 3), 25 (Emergency Patch Release 3), 26 (Emergency Patch Release 3)
Why it stays unpatched
PaperCut publishes no end-of-life calendar - support rides Maintenance & Support contracts, and whether an old line gets a fix is decided per release. This time the vendor decided in writing: the September 2026 advisory's stated path for everything before v24 is upgrade, and Emergency Patch Release 3 shipped for v24/v25/v26 only, against attacks PaperCut says it has 'observed being exploited in the wild.' The no-fix status of 23 and earlier is the vendor's declared position, not an end-of-life inference - notable because PaperCut HAS backported before (the coordinated March 2024 security release covered lines 20-22). CISA's required action includes discontinuing use where mitigations are unavailable.
CVSS 6.8
CISA KEV
EPSS 8.8% (30d)
libuser /etc/passwd race condition - a local authenticated user can corrupt /etc/passwd via a libuser-compiled application (such as userhelper), causing denial of service; chained with CVE-2015-3245 (fixed in the same errata pair) it escalates privileges to root. CISA's KEV entry describes the outcome as denial of service or privilege escalation. (Race condition (CWE-367))
End-of-life versions affected — no fix will come
5
Fixed only in
RHEL 6 (RHSA-2015:1482, 2015-07-23), RHEL 7 (RHSA-2015:1483, 2015-07-23)
Why it stays unpatched
Red Hat's own CVE record states the flaw 'affects the versions of libuser as shipped with Red Hat Enterprise Linux 5' and 'is not currently planned to be addressed in future updates' - the fix shipped only for RHEL 6 (RHSA-2015:1482) and RHEL 7 (RHSA-2015:1483). That decision was made in 2015, while RHEL 5 was in its Production 3 phase; RHEL 5 has since exited every support phase (end of production 2017-03-31, Extended Life-cycle Support ended 2020-11-30), so no fix will ever exist.
CVSS 8.9
CISA KEV
EPSS 32% (30d)
OS command injection in the SNMP monitoring component (optional zimbra-snmp package, SNMP notifications enabled): unauthenticated attacker sends specially crafted SMTP requests that result in arbitrary OS command execution as the zimbra user. Active exploitation campaign confirmed by CERT Polska 2026-08-17. (OS command injection (CWE-78))
End-of-life versions affected — no fix will come
10.0 (End of General Support 2025-06-30; last patch 10.0.18 on 2025-11-06) 9.0 (End of Technical Guidance 2025-06-30; last patch 9.0.0 P46 on 2025-06-18) 8.8.15 LTS (End of Technical Guidance 2024-12-31)
Fixed only in
10.1.20
Why it stays unpatched
The only fix release is 10.1.20. Zimbra's release index marks 10.0, 9.0 and 8.8.15 as past support, and the 2026 advisory history confirms the backport window is closed: of sixteen CVE-2026 advisory rows, fifteen list a 10.1.x fix only; the single 10.0.x fix (10.0.18, 2025-11-06) was 10.0's last patch. Framing guardrail: the defensible claim is 'no fix exists for these lines and they are past vendor support' — NOT 'these lines are confirmed exploited'. The vulnerable code path requires the optional SNMP package plus notifications enabled, which an operator can verify and disable as a stopgap; that mitigation is vendor-documented only as a precondition, not as an advisory-recommended workaround.
CVSS 9.3
CISA KEV
EPSS 16% (30d)
Unauthenticated full-read server-side request forgery in webhook delivery; URL validation bypassed via unvalidated HTTP redirects or DNS rebinding, reaching internal and cloud metadata services (Server-side request forgery (SSRF))
End-of-life versions affected — no fix will come
2 1
Fixed only in
3.15.0
Why it stays unpatched
MLflow publishes no lifecycle policy and has never announced end of life for the 2.x line. Separately: 2.x has been silent since 2.22.5 (2026-05-12) and the fix for this actively exploited flaw ships only in 3.15.0 - no 2.x release containing it exists, and no commercial extended-support vendor covers MLflow. End of life here is de facto, evidenced by release behaviour, not vendor declaration; the affected-but-never-fixed status of 2.x is documented fact.
CVSS 9.8
CISA KEV
EPSS 87% (30d)
Unauthenticated remote code execution via the agent polling protocol (Deserialization of untrusted data)
End-of-life versions affected — no fix will come
2025.07 2025.03 2024.12 2024.07 2024.03 2023.11 2023.05 2022.10 2022.04
Fixed only in
2025.11.7, 2026.1.3
Why it stays unpatched
JetBrains provides security fixes only for the current and immediately previous release lines. The fix exists solely in 2025.11.7 and 2026.1.3; every earlier line is past end of support and receives no update for this actively exploited flaw.
CVSS 5.9
CISA KEV
EPSS 29% (30d)
Symlink-based persistence that survives patching — a post-exploitation weakness abused after a threat actor has already exploited a separate filesystem-level vulnerability. KEV-listed by CISA. (Improper link resolution / persistence)
End-of-life versions affected — no fix will come
7.0 6.4
Fixed only in
7.6.2, 7.4.7
Why it stays unpatched
Fortinet's advisory FG-IR-25-934 lists 'FortiOS 7.0 all versions' and '6.4 all versions' as affected, and gives their only remediation as 'Migrate to a fixed release' — no fixed build is or will be published for either branch. FortiOS 7.0 reached end of support 2025-09-30 and 6.4 on 2024-09-30. (The current 7.2 branch is also given no build but is excluded here because it remains supported until 2026-09-30.)
CVSS 8.8
CISA KEV
EPSS 98% (30d)
Remote code execution via the Jolokia JMX-HTTP bridge — effectively unauthenticated on the 6.0 and 6.1 lines (the console's Jolokia endpoint sits outside the security constraints per CVE-2024-32114), and authenticated on the 5.x lines (Exposure of a management interface (JMX via Jolokia))
End-of-life versions affected — no fix will come
6.1 6.0 5.18 5.17 5.16
Fixed only in
5.19.4, 6.2.3
Why it stays unpatched
The fix ships only in the 5.19.x line (5.19.4) and in 6.2.3. Every ActiveMQ line below that — 6.0, 6.1, and 5.16 through 5.18 — is past end of life and receives no backport; all fall within the vendor's affected range with no available patch. The 6.0/6.1 lines are the most exposed, being effectively unauthenticated.
CVSS 9.9
CISA KEV
EPSS 99% (30d)
Authenticated remote code execution via PHP object deserialization in the file-upload handler (the _from request parameter). The vulnerable code path had been present in the codebase for roughly a decade. (Deserialization of untrusted data (RCE))
End-of-life versions affected — no fix will come
1.4 1.3 1.2
Fixed only in
1.5.10, 1.6.11
Why it stays unpatched
The fix shipped only in 1.5.10 and 1.6.11. NVD's authoritative affected range (versionStartIncluding 0, versionEndExcluding 1.5.10) places the 1.4, 1.3 and 1.2 lines within scope, and no fixed point release was issued for any of them — all three are past end of life. Basis is stated explicitly (NVD range plus the documented decade-long presence of the deserialization path); the entry is removed if a backport later appears.
CVSS 9.3
CISA KEV
EPSS 100% (30d)
Out-of-bounds read in NetScaler ADC and NetScaler Gateway when configured as a Gateway (VPN virtual server, ICA Proxy, CVPN, RDP Proxy) or AAA virtual server - insufficient input validation lets unauthenticated requests leak memory contents, including session tokens usable for session hijacking (the 'CitrixBleed 2' pattern). Widely exploited against internet-facing appliances. (Out-of-bounds read / memory over-read (CWE-125))
End-of-life versions affected — no fix will come
13.0 (all builds) 12.1 (standard; the separately-dated 12.1-FIPS variant received a build)
Fixed only in
14.1-43.56 and later, 13.1-58.32 and later, 13.1-FIPS/NDcPP 13.1-37.235 and later, 12.1-FIPS 12.1-55.328 and later (FIPS variant only)
Why it stays unpatched
Cloud Software Group's own bulletin declares the end-of-life lines vulnerable and offers them no build: standard 12.1 (EOL May 30, 2023) and all of 13.0 (EOL July 15, 2024) are stated to be vulnerable with upgrade as the only path - precision note: the 12.1-FIPS compliance variant, which carries its own later lifecycle dates, did receive a fixed build, underscoring that the standard-line omission is a lifecycle decision rather than technical impossibility. CISA added the CVE to KEV with a one-day federal remediation window (added July 10, due July 11, 2025), among the shortest on record.
CVSS 9.8
CISA KEV
EPSS 83% (30d)
Path traversal in the D-Link DIR-859 (firmware 1.06B01) HTTP POST handler /hedwig.cgi: manipulating the 'service' argument reads arbitrary files such as the DHCP configuration, exposing credentials and enabling further compromise. NVD scores it 9.8; the CVE record itself is marked 'UNSUPPORTED WHEN ASSIGNED' with the note that the vendor 'confirmed immediately that the product is end-of-life. It should be retired and replaced.' CISA added it to the KEV catalog on 2025-06-25. (Improper limitation of a pathname to a restricted directory / path traversal (CWE-22))
End-of-life versions affected — no fix will come
DIR-859
Fixed only in
—
Why it stays unpatched
D-Link answered this specific CVE with an end-of-life notice rather than a firmware release: SAP10371 names CVE-2024-0769 and states that firmware development for the DIR-859 has ceased and the device should be retired. The model's end of support (2020-12-10) predates the CVE by three years. Contrast the model's earlier flaw CVE-2019-17621, which D-Link did patch while the DIR-859 was supported (SAP10146, 'confirmed and released patches') and which is therefore deliberately NOT on this feed.
CVSS 9
CISA KEV
EPSS 100% (30d)
Stack-based buffer overflow in Ivanti Connect Secure / Pulse Connect Secure allowing a remote unauthenticated attacker to achieve remote code execution on the VPN appliance. Initially triaged by Ivanti as a non-exploitable product bug, later confirmed exploitable 'through sophisticated means' with active exploitation in the wild. (Stack-based buffer overflow (CWE-121))
End-of-life versions affected — no fix will come
Pulse Connect Secure 9.1x (9.1R18.9 and prior)
Fixed only in
Ivanti Connect Secure 22.7R2.6 and later
Why it stays unpatched
Ivanti's advisory is unusually explicit for this case: 'Pulse Connect Secure 9.1x reached End-of-Support on December 31, 2024, and no longer receives any code changes. Ivanti cannot provide guidance to customers to stay on an unsupported version. Customers' only option is to migrate to a secure platform.' Rarer still, the vendor confirmed exploitation observed on the end-of-support line itself - not inferred exposure. Ivanti's FAQ adds that reporting on EoS products is discretionary and 'Ivanti will not provide any troubleshooting or code change for products that are no longer supported.'
CVSS 9.8
CISA KEV
EPSS 100% (30d)
Path-equivalence flaw in the default servlet's partial PUT handling. Under specific configurations an unauthenticated remote attacker can view or inject content into uploaded files; with file-based session persistence at the default location plus a deserialization-gadget library on the classpath, it escalates to remote code execution. Exploitation requires writes enabled on the default servlet (disabled by default) and partial PUT support (enabled by default) - not every default install is exposed, but exploitation in the wild is established (KEV). CISA notes it can be chained with CVE-2026-34486. (Path equivalence (CWE-44); deserialization on the RCE path (CWE-502))
End-of-life versions affected — no fix will come
8.5
Fixed only in
11.0.3, 10.1.35, 9.0.99
Why it stays unpatched
Apache's own CVE record names Tomcat 8.5.0 through 8.5.100 - the entire 8.5 line, through its final release - as known affected, while the recommended fixes are 11.0.3, 10.1.35 and 9.0.99 only. Tomcat 8.5 had reached end of life on 2024-03-31, nearly a year before this CVE was published, and its final release (8.5.100) shipped 2024-03-19. Apache's 8.x security page states that vulnerabilities reported after 31 March 2024 'are not listed below and will not be fixed.' No fixed 8.5 release exists and none will come.
CVSS 7.2
CISA KEV
EPSS 54% (30d)
Command injection in the web-based management interface of the Cisco Small Business RV016, RV042, RV042G, RV082, RV320 and RV325 routers: improper validation of user input in incoming HTTP packets lets an authenticated, remote attacker send a crafted request and execute arbitrary commands with root-level privileges. Valid administrative credentials are required, which is why NVD rates it 7.2 rather than 9.8; CISA confirmed exploitation in the wild when it added the CVE to the KEV catalog on 2025-03-03, and CISA's required action includes 'discontinue use of the product if mitigations are unavailable.' (Improper neutralization of special elements used in a command (CWE-77))
End-of-life versions affected — no fix will come
RV320 RV325 RV042 RV042G RV082
Fixed only in
—
Why it stays unpatched
Cisco names six models as vulnerable and states in the advisory that it will not release software updates for them; the only mitigation is disabling remote management or restricting access to the affected feature. Every named model with a Cisco end-of-life bulletin is past its Last Date of Support (RV320/RV325 and RV042/RV042G on 2025-01-31, RV082 on 2021-05-31); RV016 is named by Cisco but carries no separate bulletin and is not modelled here. No fixed firmware exists for any of them and Cisco says none will come. The vendor's decision not to patch (stated January 2023) and the models' end-of-support dates are separate facts: the advisory predates the RV320/RV325/RV042 end of support by two years.
CVSS 6.8
CISA KEV
EPSS 27% (30d)
Active Directory integration authentication bypass — a member of a domain group named 'ESX Admins' gains full host administrative access. Exploited in the wild by ransomware operators (Akira, Black Basta). (Authentication bypass)
End-of-life versions affected — no fix will come
7.0
Fixed only in
ESXi 8.0 U3 (ESXi80U3-24022510)
Why it stays unpatched
Broadcom's own advisory matrix (VMSA-2024-0013) lists ESXi 7.0 as affected with fixed version 'No Patch Planned' — the fix ships only in 8.0 U3, and Broadcom stated in writing that 7.0 will receive no patched build. Only a manual Active Directory reconfiguration workaround exists. ESXi 7.0 reached end of general support on 2025-10-02, so no update will come.
CVSS 9.8
CISA KEV
EPSS 100% (30d)
Improper authorization allowing an unauthenticated attacker to reset Confluence and create an administrator account, leading to full compromise. Mass-exploited (including ransomware) since November 2023. (Improper authorization)
End-of-life versions affected — no fix will come
7.0–7.18 (non-LTS) 6.x 5.x
Fixed only in
7.19.16, 8.3.4, 8.4.4, 8.5.3, 8.6.1
Why it stays unpatched
The only 7.x fix shipped on the 7.19 LTS line (7.19.16); every earlier non-LTS 7.x branch and all of 6.x and 5.x fall under the advisory's 'all versions prior to the listed fix versions' and received no fixed release for this actively exploited authorization bypass. All are past end of life (Confluence Server as a whole reached end of life 2024-02-15). This is a distinct CVE from the other Confluence entries; the 8.0–8.2 branches are deliberately excluded as a normal non-LTS lifecycle case rather than an abandoned-branch one.
CVSS 9.8
CISA KEV
EPSS 80% (30d)
Remote command execution in the D-Link DIR-820L (firmware 1.05B03, the last release): an unauthenticated HTTP POST to the get/set ccp handler injects OS commands (CWE-78). NVD scores it 9.8. CISA added it to the KEV catalog on 2022-09-08 with the required action 'The impacted product is end-of-life and should be disconnected if still in use.' (OS command injection (CWE-78))
End-of-life versions affected — no fix will come
DIR-820L
Fixed only in
—
Why it stays unpatched
1.05B03 is the final DIR-820L firmware and the version NVD names as affected. D-Link's EOL notice states that all firmware development for the model ceased, and its June 2026 notice SAP10508 lists DIR-820L again among the legacy EOL/EOS routers being compromised by the AryStinger botnet, with the same instruction: retire and replace. CISA's required action for this CVE is to disconnect the device. The model's end of support (2017-11-01) predates the CVE by more than four years; D-Link has never issued a fix and says it will not develop one.
CVSS 9.8
CISA KEV
EPSS 100% (30d)
Unauthenticated OGNL injection allowing remote code execution. Mass-exploited in the wild since June 2022. (OGNL expression injection (RCE))
End-of-life versions affected — no fix will come
6.x
Fixed only in
7.4.17, 7.13.7, 7.14.3, 7.15.2, 7.16.4, 7.17.4, 7.18.1
Why it stays unpatched
Atlassian's advisory names every release after 1.3.0 as affected but shipped fixes only on the 7.4 and 7.13–7.18 branches. Confluence 6.x was already past end of life at the June 2022 disclosure and received no fixed build for this actively exploited RCE. (Confluence Server as a whole reached end of life 2024-02-15.) Branches that did receive a per-branch backport are deliberately excluded.
CVSS 9.8
CISA KEV
EPSS 100% (30d)
Improper validation of the recipient address in deliver_message() allowing remote command execution as root ('Return of the WIZard'). Mass-exploited in the wild. (Improper input validation (RCE))
End-of-life versions affected — no fix will come
4.91
Fixed only in
4.92
Why it stays unpatched
The Exim advisory names 4.87 through 4.91 as affected and delivers the fix only as the forward 4.92 release — no patched build was issued for the 4.91 line, which reached end of life 2019-02-10. Under Exim's model the only remediation is to upgrade off the dead branch.
CVSS 7.2
CISA KEV
EPSS 84% (30d)
Remote code execution via the DataImportHandler dataConfig request parameter, which accepts a full DIH configuration including a script transformer. (Unsafe configuration accepted at request time (RCE))
End-of-life versions affected — no fix will come
7 6 5
Fixed only in
8.2.0
Why it stays unpatched
The mitigation exists only from Solr 8.2.0 onward; no fixed release was issued for the 7.x, 6.x or 5.x lines, all past end of life. The DataImportHandler that carries the flaw shipped in every one of these versions, and none received a backport.
CVSS 9.8
CISA KEV
EPSS 100% (30d)
Unauthenticated OGNL injection allowing remote code execution. Widely exploited since 2021 and on CISA's KEV catalog. (OGNL expression injection (RCE))
End-of-life versions affected — no fix will come
6.0–6.12
Fixed only in
6.13.23, 7.4.11, 7.11.6, 7.12.5, 7.13.0
Why it stays unpatched
Atlassian's advisory lists the 4.x, 5.x and 6.0–6.12 lines among affected versions but issued fixed builds only on 6.13, 7.4, 7.11, 7.12 and 7.13. The 6.0–6.12 lines were past end of life at disclosure and received no fixed build for this actively exploited RCE. The 6.13 branch, which did receive a backport, is excluded.
CVSS 9.8
CISA KEV
EPSS 96% (30d)
Forced OGNL double-evaluation of attacker-supplied input allowing remote code execution (S2-061). (OGNL expression injection (RCE))
End-of-life versions affected — no fix will come
2.3
Fixed only in
2.5.26
Why it stays unpatched
S2-061 lists the affected range as Struts 2.0.0 through 2.5.25 and ships the fix only in 2.5.26. The Struts 2.3 line ended at 2.3.37 and reached end of life on 2019-05-14 — eighteen months before this advisory — so no 2.3.x fix was ever released. A 2.3.x install cannot patch in place. (The 2.5 line is excluded: 2.5.26 is a same-line fix and 2.5 was supported until 2024-04-30.)
CVSS 7.5
CISA KEV
EPSS 99% (30d)
Remote code execution via the VelocityResponseWriter when params.resource.loader.enabled is set, allowing a Velocity template to be supplied and executed. (Server-side template injection (RCE))
End-of-life versions affected — no fix will come
7 6 5
Fixed only in
8.4
Why it stays unpatched
The vulnerable parameters-based resource loader was removed only in Solr 8.4; no fixed release was issued for the 7.x, 6.x or 5.x lines (the 7.x line ended at 7.7.2), all past end of life. Every one of these versions is inside the vendor's 5.0.0–8.3.1 affected range with no available patch.
Methodology
This feed exists because two datasets that answer half the question each normally live in separate worlds. CISA's Known Exploited Vulnerabilities catalog tells you a vulnerability is being exploited in the wild. Lifecycle data tells you whether a given version still receives fixes. The dangerous case — exploited and unpatchable — is where they overlap, and until you join them by hand, no single source shows it.
How each entry is verified
For every entry we confirm, from primary sources: (1) the CVE is on CISA's KEV catalog; (2) the vendor's security advisory lists the specific version as affected; (3) that version is past its end-of-life date in our verified lifecycle data; and (4) the vendor's fix ships only in supported versions, leaving the end-of-life line without an update. Every entry links its KEV record, the vendor advisory, the NVD detail, and our lifecycle page so you can check our work. Each carries the date it was last reviewed.
What this is not
We do not detect exploitation ourselves — that signal comes from CISA. We do not publish exploit code, proof-of-concept detail, or anything that is not already public in the sources we link. This is an aggregation of public facts, arranged so defenders can answer one specific question — "is anything in my stack both actively exploited and past the point of a fix?" — in one place instead of five.
When an entry disappears
Vendors occasionally ship an out-of-band fix for an end-of-life version. When that happens, the entry no longer qualifies and is removed — because the claim on this page must stay true. A shrinking list is a feature: it means a fix arrived where none was expected.
Using the data
The full feed is available as JSON at /exploited-and-unpatchable.json, free, with attribution to endoflife.ai. Version-level risk scoring for any product is in the API (/v1/score/{product}/{version} returns the EOL date, days past EOL, CISA KEV exposure, and the EOL Risk Score in one call). Building lifecycle-aware security tooling and want a richer or commercially-licensed feed? Start a commercial conversation →