PaperCut NG/MF End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all PaperCut NG/MF versions. Dates read at the vendor's own lifecycle pages (papercut.com). Updated at every deploy.
PaperCut NG/MF 26 is supported, with no end-of-life or end-of-support date announced yet. The next PaperCut NG/MF version to reach end of life is 23, on December 31, 2026. 4 of 8 tracked PaperCut NG/MF versions are past end of life; the most recent to reach it, 22, did so on December 31, 2025. The full PaperCut NG/MF lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 19 | 19.2.7 | Apr 9, 2019 | Dec 31, 2022 | 1385 days past EOL | EOL |
| 20 | 20.1.10 | Jun 24, 2020 | Mar 31, 2024 | 929 days past EOL | EOL |
| 21 | 21.2.14 | Apr 13, 2021 | Nov 30, 2024 | 685 days past EOL | EOL |
| 22 | 22.1.5 | Jun 29, 2022 | Dec 31, 2025 | 289 days past EOL | EOL |
| 23 | 23.0.9 | Oct 30, 2023 | Dec 31, 2026 | 76 days remaining | Warning |
| 24 | 24.1.10 | Aug 1, 2024 | TBD | Supported | Active |
| 25 | 25.0.13 | Aug 12, 2025 | TBD | Supported | Active |
| 26 | 26.0.5 | Jun 30, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/papercut-ng-mf)
PaperCut NG/MF lifecycle status — the real story
PaperCut NG/MF is one of the most widely deployed print-management platforms in education, healthcare and enterprise. Majors ship approximately annually, and PaperCut announces the end of support for each major line on its support end-of-life policy and announcements page (last updated September 28, 2026), with two dates per line: one for customers without current Maintenance & Support and a later one for customers with it. For version 23 (announced 1 July 2026) the page reads: "We will be ending support for these versions on: 30th September 2026 (customers without current M&S) 31st December 2026 (customers with current M&S)". The urgent security advisory (last updated September 10, 2026) draws a narrower line for fixes: asked "Will there be a release for NG/MF 23 and earlier?", it answers "There are no emergency patches or maintenance releases for version 23 or earlier" and points customers to "a currently supported version line (24, 25 or 26)". The patched builds are the maintenance releases 26.0.5, 25.0.13 and 24.1.10, all published September 10, 2026.
The two vulnerabilities driving this, CVE-2026-82078 (9.4 Critical, unsafe dynamic class loading) and CVE-2026-81578 (8.8, authentication bypass), chain into unauthenticated remote code execution and were added to CISA's Known Exploited Vulnerabilities catalog on August 31, 2026 with a federal remediation deadline of September 14, 2026 — and a required action that includes discontinuing use of the product if mitigations are unavailable. For versions 23 and earlier, no mitigation ships: the vendor's stated path is upgrade. Notably, PaperCut has backported before — the coordinated March 2024 security release shipped fixes for lines 20 through 22 — which makes the September 2026 upgrade-only stance a deliberate boundary, not an oversight.
Field mapping: eol is the later date on PaperCut's end-of-life page, the day support ends for customers with current Maintenance & Support, after which PaperCut does not support the line at all; support is the earlier date, the day support ends for customers without current M&S. Versions 19 to 22 have passed both dates. Version 23 has passed the first (September 30, 2026) and is supported for customers with current M&S until December 31, 2026, but it receives no fix for the exploited CVE-2026-82078 and CVE-2026-81578 chain: the advisory names 24, 25 and 26 as the supported lines with patched releases, so a version 23 server is unpatched now even while its support window is open. Lines 24, 25 and 26 have no end date announced. Release dates come from PaperCut's complete release-history index (first listed release per line); the latest build per line is the newest one listed there.
PaperCut NG/MF release and support pattern
Across the 8 release lines with a published release date, PaperCut NG/MF has shipped a new line roughly every 1 year (median interval). A line typically stays supported for about 3.6 years from its release to its end-of-life date (measured on the 5 lines with both dates published).
Of the 8 release lines tracked, 4 are past end of life and 4 are still within support. The newest line, 26, was released June 30, 2026. The next scheduled end of life is 23 on December 31, 2026 — 75 days from this build.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
PaperCut NG/MF security intelligence
CISA KEV history: PaperCut NG/MF is named in CISA's Known Exploited Vulnerabilities catalog 5 times, most recently on 2026-08-31, including use in ransomware campaigns. Derived from CISA's live catalog at every build.
What does PaperCut NG/MF end of life mean for your organization?
When a version of PaperCut NG/MF reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL PaperCut NG/MF should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when PaperCut NG/MF reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL PaperCut NG/MF versions. This is a bridge, not a permanent solution — plan your migration in parallel.
PaperCut NG/MF has 4 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for PaperCut NG/MF is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."