privatebin end of life dates — full support timeline
8 of 9 tracked privatebin releases have already reached end of life. The dates below are published support dates, not estimates.
Version support timeline
| Release | Released | End of life | Latest | Status |
|---|---|---|---|---|
| 2.0 | 2025-07-28 | not announced | 2.0.5 | supported |
| 1.7 | 2024-02-11 | 2025-07-28 | 1.7.9 | ended |
| 1.6 | 2023-09-11 | 2024-02-12 | 1.6.2 | ended |
| 1.5 | 2022-12-11 | 2023-09-12 | 1.5.2 | ended |
| 1.4 | 2022-04-09 | 2022-12-11 | 1.4.0 | ended |
| 1.3 | 2019-07-09 | 2022-04-09 | 1.3.5 | ended |
| 1.2 | 2018-07-22 | 2019-07-10 | 1.2.3 | ended |
| 1.1 | 2016-12-26 | 2018-07-22 | 1.1.1 | ended |
| 1.0 | 2016-08-25 | 2016-12-26 | 1.0 | ended |
Who is affected
Anyone running an unsupported privatebin release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.
Source
These dates are maintained by endoflife.date/privatebin, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next privatebin deadline
You are reading this because a privatebin release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every privatebin and related deadline as it is announced, with exact dates and primary sources.
Watch privatebin deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.