DEV Community: endoflife-ai

Bitbucket 9.1 Dies August 27, 2026 — and a Bitbucket Version Dies Every Month Through Year-End

endoflife-ai — Mon, 17 Aug 2026 15:25:01 +0000

Bitbucket Data Center 9.1 reaches end of support on August 27, 2026, exactly two years after release — and Atlassian's two-year clock retires 9.2 in September, 9.3 in October, and the 9.4 LTS in December. Why the KEV history makes unpatched Bitbucket a proven target, and why 10.2 LTS is the upgrade that skips the treadmill.

The monthly cascade

Version	Released	End of support	Time left at publication	Risk score
9.1	2024-08-27	2026-08-27	11 days	45
9.2	2024-09-24	2026-09-24	39 days	45
9.3	2024-10-29	2026-10-29	74 days	45
9.4 (LTS)	2024-12-02	2026-12-03	109 days	38
10.2 (LTS)	2026-03-03	2028-03-03	18+ months	30

What's covered

The monthly cascade
Why unpatched Bitbucket is a proven target, not a theoretical one
Skip the treadmill: 10.2 LTS or the ladder

Full guide with every version, risk scores, and live updates: https://endoflife.ai/article-bitbucket-91-eol

The Whole Proxmox 8 Era Ends August 31, 2026 — VE, Backup Server, and Mail Gateway Together

endoflife-ai — Mon, 17 Aug 2026 15:24:28 +0000

Proxmox VE 8, Proxmox Backup Server 3, and Proxmox Mail Gateway 8 all reach end of life on August 31, 2026 — the same day, because all three ride Debian 12's security lifecycle. It is the third time the whole family has retired in lockstep. Every date, the pattern, and the upgrade paths to the 9/4-era.

Lockstep is the policy, not a coincidence

Generation	Debian base	VE	Backup Server	Mail Gateway	Family EOL
8-era	Debian 12	8	3	8	2026-08-31
7-era	Debian 11	7	2	7	2024-07-31
6-era	Debian 10	6	1*	6	2022-09-30

What's covered

Lockstep is the policy, not a coincidence
What runs out, and where it bites
The upgrade order that avoids a bad weekend

Full guide with every version, risk scores, and live updates: https://endoflife.ai/article-proxmox-8-family-eol

NumPy 2.1 End of Life: August 19, 2026 — and the Same Day, Python 3.11 Falls Off NumPy's Floor

endoflife-ai — Mon, 17 Aug 2026 15:24:27 +0000

NumPy 2.1 reaches end of life on August 19, 2026 under NEP 29's 24-month rule. The same schedule drops Python 3.11 from NumPy's support floor that day (3.12+ / 2.2+ from August 19), even though Python 3.11 itself lives to October 2027. And if you are still on Python 3.10, your last supported NumPy died in June 2025. Two clocks, every date, and what to do.

The NumPy clock: 24 months, every version

Version	Released	End of life	Latest	Risk score
2.5	2026-06-21	2028-06-22	2.5.2	10
2.4	2025-12-20	2027-12-21	2.4.6	10
2.3	2025-06-07	2027-06-08	2.3.5	10
2.2	2024-12-08	2026-12-09	2.2.6	18
2.1	2024-08-18	2026-08-19	2.1.3	25
2.0	2024-06-16	2026-06-17	2.0.2	35

What's covered

The NumPy clock: 24 months, every version
The Python clock: the floor that moves the same day
If you are on Python 3.10, your NumPy died last June
What to do

Full guide with every version, risk scores, and live updates: https://endoflife.ai/article-numpy-21-eol

Grafana 12.3 End of Life: August 19, 2026 — and 12.4 Outlives Every Grafana 13

endoflife-ai — Sun, 16 Aug 2026 15:21:06 +0000

Grafana 12.3 reaches end of life on August 19, 2026 — exactly nine months after release. Grafana's 15-month window only applies to the last minor of a major line, which is why 12.4 (EOL May 24, 2027) outlives both Grafana 13.0 and 13.1. Every date, verified against Grafana's own support policy.

The nine-month rule and the fifteen-month exception

Version	Released	Active support ended	End of life	Lifespan	Risk score
12.4 last 12.x	2026-02-24	2026-04-17	2027-05-24	15 months	40
12.3	2025-11-19	2026-02-24	2026-08-19	9 months	55
12.2	2025-09-23	2025-11-19	2026-06-23	9 months	65
12.1	2025-07-22	2025-09-23	2026-04-22	9 months	70
12.0	2025-05-05	2025-07-22	2026-02-05	9 months	70

What's covered

What stops on August 19
The nine-month rule and the fifteen-month exception
Why 12.4 outlives Grafana 13.0 and 13.1
What is already dead — and why unpatched Grafana is a target
What to do

Full guide with every version, risk scores, and live updates: https://endoflife.ai/article-grafana-123-eol

IBM i End of Life: 7.4 Has 49 Days of Standard Support Left — and Whether You Call It AS/400, iSeries, or IBM i, the Clock Is th

endoflife-ai — Sat, 15 Aug 2026 15:20:38 +0000

IBM i 7.4 reaches end of standard support September 30, 2026 — the same day Oracle JDK 17 Premier Support and FortiOS 7.2 expire, and the same day IBM i 7.3's first Service Extension window closes. Every release's dates from 1988's AS/400 to 7.6, the paid Service Extension ladder (7.3 to 2028, 7.4 announced to 2029), and the hardware coupling: Power7 tops out at 7.3, Power8 at 7.4, and 7.6 needs Power10.

IBM i release dates and end-of-support dates: every version since 1988

Release	Status	Released	End of Support (EOL)	Extended support ends	Notes
IBM i 7.6	Supported	Apr 18, 2025	Not announced	Available	Current release. Requires Power10 or Power11 — Power9 cannot run it.
IBM i 7.5	Supported	May 10, 2022	Not announced	Available	No announced date; per IBM's policy the date arrives with at least 12 months' notice. Requires Power9 or later.
IBM i 7.4	Warning	Jun 21, 2019	Sep 30, 2026	Sep 30, 2029†	49 days of standard support left at publication. The newest release Power8 can run.
IBM i 7.3	EOL	Apr 15, 2016	Sep 30, 2023	Sep 30, 2028	Two-rung extension ladder: first window ends Sep 30, 2026, extended tier to 2028. Power7's ceiling.
IBM i 7.2	EOL	May 2, 2014	Apr 30, 2021	Apr 30, 2026	Fully dead — the extended Service Extension closed April 30, 2026.
IBM i 7.1	EOL	Apr 23, 2010	Apr 30, 2018	Apr 30, 2024†	First Technology Refresh-era release; IBM lists its extension as available through April 2024.
IBM i 6.1	EOL	Mar 21, 2008	Sep 30, 2015	Sep 30, 2019	Covers machine-code levels V6R1M0 and V6R1M1 per IBM's lifecycle notes.
V5R4 (5.4)	EOL	Feb 14, 2006	Sep 30, 2013	Sep 30, 2017	Eleven and a half years from GA to the end of its extension — the ladder is not new.
V5R3 (5.3)	EOL	Jun 11, 2004	Apr 30, 2009	Apr 30, 2013
V5R2 (5.2)	EOL	Aug 30, 2002	Apr 30, 2007	—
V5R1 (5.1)	EOL	May 25, 2001	Sep 30, 2005	—	First release whose dates land on the April 30 / September 30 rhythm.
V4R5 (4.5)	EOL	Jul 28, 2000	Jul 31, 2002	Dec 31, 2002
V4R4 (4.4)	EOL	May 21, 1999	May 31, 2001	Nov 30, 2001
V4R3 (4.3)	EOL	Sep 11, 1998	Jan 31, 2001	—
V4R2 (4.2)	EOL	Feb 27, 1998	May 31, 2000	Jan 31, 2001
V4R1 (4.1)	EOL	Aug 29, 1997	May 31, 2000	—
V3R7 (3.7)	EOL	Nov 8, 1996	Jun 30, 1999	—
V3R2 (3.2)	EOL	Jun 21, 1996	May 31, 2000	—	Shipped out of sequence — GA after V3R6, and outlived it by 19 months.
V3R6 (3.6)	EOL	Dec 22, 1995	Oct 31, 1998	—
V3R1 (3.1)	EOL	Nov 25, 1994	Oct 31, 1998	—
V3R0.5 (3.0)	EOL	Jun 3, 1994	May 31, 1997	—
V2R3 (2.3)	EOL	Dec 17, 1993	May 31, 1996	—
V2R2 (2.2)	EOL	Sep 18, 1992	Mar 31, 1995	—
V2R1 (2.1)	EOL	Mar 6, 1992	Jun 30, 1994	—	Oldest cycle in our tracked data; IBM's own table reaches back to Rel 1, GA August 26, 1988.

What's covered

How the IBM i lifecycle actually works: one clock per release, Technology Refreshes inside it
IBM i release dates and end-of-support dates: every version since 1988
September 30: the triple cliff, and the ladder behind it
The hardware coupling: your Power generation decides your OS ceiling
AS/400, iSeries, System i, IBM i: three renames, one lifecycle table
The two-hop trap: why waiting on IBM i compounds

Full guide with every version, risk scores, and live updates: https://endoflife.ai/article-ibm-i-eol

Oracle 19c End of Support Date: December 31, 2029 — a Date That Already Moved Once, and the Trap Waiting in 21c

endoflife-ai — Sat, 15 Aug 2026 15:20:05 +0000

Oracle Database 19c Premier Support ends December 31, 2029; Extended Support runs to December 31, 2032 — dates Oracle extended in November 2024 from the original April 2024/2027 schedule. Why 'upgrading' 19c to 21c lands on a version that dies July 31, 2027 — earlier than 19c itself — and the honest 23ai/26ai path.

Every Oracle Database version's support dates

Release	Released	Premier Support ends (EOL)	Extended Support ends	Status
23ai / 26ai (Long Term)	Sep 19, 2023	Dec 31, 2031	TBD	Supported
21c (Innovation)	Aug 13, 2021	Jul 31, 2027	Not offered	Supported
19c (Long Term)	Apr 25, 2019	Dec 31, 2029	Dec 31, 2032	Supported
18c	Jul 23, 2018	Jun 30, 2021	Not offered	EOL
12c Release 2 (12.2)	Mar 1, 2017	Mar 31, 2022	Not offered	EOL
12c Release 1 (12.1)	Jun 25, 2013	Jul 31, 2018	Jul 31, 2022	EOL
11g Release 2 (11.2)	Sep 1, 2009	Jan 31, 2015	Dec 31, 2020	EOL
11g Release 1 (11.1)	Aug 9, 2007	Aug 31, 2012	Aug 31, 2015	EOL
10g Release 2 (10.2)	Jul 11, 2005	Jul 31, 2010	Jul 31, 2015	EOL
10g Release 1 (10.1)	Sep 8, 2003	Jan 31, 2009	Jan 1, 2012	EOL
9i Release 2 (9.2)	May 1, 2002	Jul 31, 2007	Jul 31, 2010	EOL
9i Release 1 (9.0)	Jun 1, 2001	Dec 31, 2003	Not offered	EOL

What's covered

The end-of-support date that already moved once
The 21c trap: the newer release dies first
Every Oracle Database version's support dates
Who is still on 19c — and why that is not an accident
What actually stops at each phase boundary
The path off 19c: 23ai — which is now called 26ai
Extended Support: what it costs, and when the answer is "you can't"

Full guide with every version, risk scores, and live updates: https://endoflife.ai/article-oracle-19c-eol

React のサポート期限はいつまで？公式の EOL 日は存在しません【2026年8月版】

endoflife-ai — Sat, 15 Aug 2026 15:20:04 +0000

React には公式のサポート期限（EOL 日）が存在しません。React 19・18・17・16・15 の公開日・最終リリース日・EOL リスクスコアを一覧で整理し、「期限がない」ことが安心材料ではない理由、React 18 の「凍結」状態の見分け方、CVE-2025-55182 の正確な影響範囲、稟議や保守契約で使える判断材料までを日本語で解説します。

React 全メジャーバージョンの状況一覧【2026年8月時点】

メジャーバージョン	公開日	アクティブサポート終了（後継メジャーの公開日）	最終リリース	公式の EOL 日	EOL リスクスコア
React 19	2024-12-05	現行バージョン	19.2.8 · 2026-07-21	公表なし	40
React 18	2022-03-29	2024-12-05（React 19 公開）	18.3.1 · 2024-04-26	公表なし	62
React 17	2020-10-20	2022-03-29（React 18 公開）	17.0.2 · 2021-03-22	公表なし	70
React 16	2017-09-26	2020-10-20（React 17 公開）	16.14.0 · 2020-10-14	公表なし	70
React 15	2016-04-07	2017-09-26（React 16 公開）	15.7.0 · 2020-10-14	公表なし	70

What's covered

React に「サポート期限」がない — まず事実を整理する
React 全メジャーバージョンの状況一覧【2026年8月時点】
「期限がない」＝「無期限サポート」ではない — React 18 は「凍結」状態
EOL リスクスコアで見る React — 採点の内訳
CVE-2025-55182 と IPA 注意喚起 — 影響範囲を正確に把握する
「期限がない」製品をどう稟議に載せるか — 日本の現場向けの判断材料
移行の進め方 — 18→19 と 16/17→19
よくある質問

Full guide with every version, risk scores, and live updates: https://endoflife.ai/article-react-lifecycle-ja

Palo Alto End of Life Has Two Clocks: Every PAN-OS Software Date, the Hardware Dates People Actually Search For, and Why 11.0 Di

endoflife-ai — Fri, 14 Aug 2026 15:52:17 +0000

Palo Alto end of life runs on two clocks. Software: PAN-OS 11.2 dies May 2, 2027 — one day before the older 11.1 — and 10.2 already passed August 27, 2025. Hardware: the PA-5250 (PA-5200 Series) reached end of sale August 31, 2023 and hits hardware EOL August 31, 2028, capped at PAN-OS 11.2 forever. Every version's dates, the 12-entry CISA KEV record, and where to land.

Clock two, hardware: end of sale, hardware end of life, and the last supported OS

Hardware platform	End of sale	Hardware end of life	Last supported OS	Recommended replacement
PA-5200 Series (PA-5220, PA-5250, PA-5260, PA-5280)	Aug 31, 2023	Aug 31, 2028	PAN-OS 11.2	PA-5400 / PA-5500 Series
PA-3200 Series (PA-3220, PA-3250, PA-3260)	Aug 31, 2023	Aug 31, 2028	PAN-OS 11.1	PA-3400 Series
PA-800 Series (PA-820, PA-850)	Aug 31, 2024	Aug 31, 2029	PAN-OS 11.1	PA-1400 Series
PA-220	Jan 31, 2023	Jan 31, 2028	PAN-OS 10.2	PA-400 / PA-500 Series
PA-7000 Series	Dec 31, 2025	Dec 31, 2030	PAN-OS 11.2	PA-7500, PA-5450

What's covered

Clock one, software: every PAN-OS release gets its own individually assigned death date
Clock two, hardware: end of sale, hardware end of life, and the last supported OS
The 11.0 lesson: release-train math, not version numbers
The May 2027 twin cliff: 11.1 and 11.2, twenty-four hours apart, in reverse order
The KEV record: what end-of-fixes means on this specific product
Every PAN-OS version's dates
The decision fork: 12.1, 12.2 — or new hardware

Full guide with every version, risk scores, and live updates: https://endoflife.ai/article-panos-eol

CVSS 9.8, EPSS 10.7%, and Confirmed Exploited: When the Three Scores Disagree

endoflife-ai — Fri, 14 Aug 2026 15:51:44 +0000

CVSS says how bad, CISA KEV says whether it is being exploited, EPSS says how likely it is next. On our Exploited & Unpatchable feed they openly disagree — a confirmed-exploited FortiOS flaw sits at 1.26% EPSS while a TeamCity flaw at CVSS 9.8 sits at 10.7%. How to read all three, and what changes when the software is end-of-life.

The three questions, precisely stated

Signal	Question it answers	Tense	Who produces it
CVSS	How bad would this be if exploited?	Conditional	The vendor (as CNA) and/or NVD
CISA KEV	Is this being exploited, in reality?	Past & present	CISA, on evidence
EPSS	How likely is exploitation in the next 30 days?	Forecast	FIRST.org, a daily model

What's covered

The three questions, precisely stated
Twelve vulnerabilities, scored three ways
Case 1: confirmed exploited, lowest probability in the set
Case 2: the highest severity, near the bottom for probability
Case 3: the medium-severity flaw ransomware crews preferred
The fourth disagreement: the scorers disagree with each other
The column that changes the answer
How to actually triage

Full guide with every version, risk scores, and live updates: https://endoflife.ai/article-scores-disagree

Mattermost 10.11 Ends August 15, 2026 — and the Newest Release Is the Wrong Upgrade

endoflife-ai — Fri, 14 Aug 2026 15:51:43 +0000

Mattermost 10.11 reaches end of life on August 15, 2026. It is one of only two releases in 55 that got a twelve-month support window instead of the usual three — and the newest release, 11.9, expires in 62 days. The upgrade that buys you the most time is an older version. Every date, and why.

The three-month rule, and the two exceptions

Support window	Releases	What it means
3 months	42	The standard. Roughly one release of overlap.
4 months	4	Minor schedule slippage.
9–10 months	7	Older, longer-cadence releases.
12 months	2	The only two releases ever given a full year — 10.11 and 11.7.

What's covered

What actually stops on August 15
The three-month rule, and the two exceptions
The LTS label points at the wrong versions
Why "upgrade to the latest" costs you time
What is still supported on August 16
What to do

Full guide with every version, risk scores, and live updates: https://endoflife.ai/article-mattermost-eol

The TeamCity RCE Under Active Exploitation Will Never Be Patched on Nine Version Lines — CVE-2026-63077

endoflife-ai — Thu, 13 Aug 2026 15:59:29 +0000

CVE-2026-63077, a CVSS 9.8 unauthenticated remote code execution flaw in JetBrains TeamCity's agent polling protocol, entered CISA's Known Exploited Vulnerabilities catalog on August 5, 2026. The fix exists only in 2025.11.7 and 2026.1.3 — nine end-of-life version lines, from 2022.04 through 2025.07, will never receive it. What a compromised CI server means, and the upgrade-or-isolate decision.

Which versions get a fix — and which are permanently exposed

Version line	Status	Released	End of life	Fix for CVE-2026-63077?
2026.1	Supported	May 11, 2026	—	Yes — 2026.1.3
2025.11	Supported	Nov 27, 2025	—	Yes — 2025.11.7
2025.07	EOL	Jul 23, 2025	May 11, 2026	Never
2025.03	EOL	Mar 20, 2025	Nov 27, 2025	Never
2024.12	EOL	Dec 5, 2024	Jul 23, 2025	Never
2024.07	EOL	Jul 18, 2024	Mar 20, 2025	Never
2024.03	EOL	Mar 27, 2024	Dec 5, 2024	Never
2023.11	EOL	Nov 28, 2023	Jul 18, 2024	Never
2023.05	EOL	May 26, 2023	Mar 27, 2024	Never
2022.10	EOL	Oct 27, 2022	Nov 28, 2023	Never
2022.04	EOL	Apr 28, 2022	May 26, 2023	Never

What's covered

Your build server is your most-trusted machine
Thirty seconds: which TeamCity are you running?
Which versions get a fix — and which are permanently exposed
The upgrade-or-isolate decision

Full guide with every version, risk scores, and live updates: https://endoflife.ai/article-teamcity-cve-2026-63077

Confluence Server End of Life: Two Years Past Support, Three Exploited CVEs, and No Patch Ever Coming

endoflife-ai — Thu, 13 Aug 2026 15:58:56 +0000

Confluence Server reached end of life on February 15, 2024 — and three actively-exploited, CISA-KEV-listed CVEs (CVE-2021-26084, CVE-2022-26134, CVE-2023-22518) were each fixed only on then-supported branches. Every end-of-life Confluence branch still running carries at least one of them permanently; a 6.x server carries all three. All three are flagged by CISA for known ransomware campaign use. The full wave-by-wave record, version dates, and the honest way out.

The scoreboard: three waves, one pattern

Wave	CVE	What it is	Severity	KEV added	Fixed only on	Left permanently vulnerable
2021	CVE-2021-26084	Unauthenticated OGNL injection → RCE	9.8 (NVD)	Nov 3, 2021	6.13, 7.4, 7.11, 7.12, 7.13 branches	6.0–6.12 (4.x/5.x also named affected)
2022	CVE-2022-26134	Unauthenticated OGNL injection → RCE	9.8 (NVD)	Jun 2, 2022	7.4 and 7.13–7.18 branches	6.x (every release after 1.3.0 affected)
2023	CVE-2023-22518	Improper authorization → instance reset, attacker-created admin account	9.8 (NVD); 10.0 (Atlassian, revised)	Nov 7, 2023	7.19.16, 8.3.4, 8.4.4, 8.5.3, 8.6.1	7.0–7.18 (non-LTS), 6.x, 5.x

What's covered

Wave one, 2021: CVE-2021-26084 — and everything before 6.13 is left behind
Wave two, 2022: CVE-2022-26134 — same flaw class, same triage, new casualties
Wave three, 2023: CVE-2023-22518 — the ransomware wave
The scoreboard: three waves, one pattern
Why this keeps happening: the lifecycle math
What to actually do

Full guide with every version, risk scores, and live updates: https://endoflife.ai/article-confluence-cve-exposure