Check Point Jumbo Hotfix Accumulators and recommended releases
What a Take is, how Check Point designates the recommended release and the recommended Jumbo Hotfix, and why Patcharo keeps both apart from support status.
Updated 30 Sept 2026Data on this page last verified 30 Sept 2026 at 00:17 UTC
Major release, Jumbo Hotfix Accumulator, Take
Check Point publishes major releases (R81.20, R82, R82.10 and so on) and, for each of them, a Jumbo Hotfix Accumulator: one cumulative package of fixes, identified by a Take number. A higher Take contains the fixes of the lower ones. Each Take carries a release date on the Jumbo Hotfix Accumulator page of its release; a Take the vendor withdraws or marks as not for deployment leaves what can be installed and is never recommended. On a gateway, the installed level is therefore a pair: the major release and the Take.
The recommended release
The article sk95746, Check Point Recommended Version and Release Terminology, names one recommended version for all deployments, to be run with its latest Jumbo Hotfix Accumulator Take. This is the release recommendation: the answer to which major release to run. It is not the newest release: a newer release can be generally available without being the recommended one. Patcharo reads this statement with its date and keeps the vendor's wording.
How Check Point designates recommended Takes
Until 2026, Check Point declared specific Takes as Recommended on a given date (the Jumbo Hotfix Accumulator page reads declared as Recommended on a date); the recommended maintenance level of a branch was that designated Take, even when newer Takes existed. In September 2026, sk95746 changed the rule: each Jumbo Hotfix Accumulator is considered Recommended from the day of its release. Under this rolling policy, the recommended maintenance level of a branch is its latest released Take that the vendor has not withdrawn. Patcharo records which policy the vendor states, with the date of the statement, and applies it branch by branch.
Designated Takes kept as history
The last Take specifically designated as Recommended on each branch stays visible as history, with its designation date, so that a gateway frozen on it can be read in context. Patcharo also keeps its own history of the vendor's statements: when the recommended release or the recommended Take of a branch changes, the previous statement is kept with the dates between which it was current.
Why latest, recommended and supported are kept apart
The release recommendation and the branch maintenance recommendation answer two different questions. A gateway on R81.20 is compared with the R81.20 maintenance recommendation even though the recommended release is a newer branch: it can be at the recommended Take of its branch and behind the recommended release at the same time. Support status is a third, separate axis: a supported branch is not necessarily recommended, and the latest release is not automatically the recommended one. Patcharo never infers a recommendation from a higher version number.
How to read the statements below
Below are the vendor's current statements as Patcharo last read them: the recommended version, then one maintenance statement per branch with its policy, the last specifically designated Take, withdrawn Takes when the vendor states any, the history of changes, the source page and the verification date.
Current statements
The vendor's own statement about what to run, with its date and source. Separate from vulnerabilities and from support status: being behind a recommendation is not a vulnerability, and a supported release is not necessarily the recommended one.
Recommended release
R82.10 · since 16 Sept 2026
Vendor wording: “Check Point Recommended version for all deployments (with its latest Jumbo Hotfix Accumulator Take)”
Source: sk95746last verified by Patcharo 30 Sept 2026 at 00:17 UTC
Recommended maintenance build per branch
R82.10
R82.10 Take 45 · since 22 Sept 2026
Vendor wording: “Each Jumbo Hotfix Accumulator is considered Recommended from the day of its release”
Policy: each newly released build is recommended from its release · stated 16 Sept 2026
Last build specifically declared as recommended: Take 40, on 10 Aug 2026 (kept as history)
History of the statement
- R82.10 Take 45 · current since 22 Sept 2026 · first read by Patcharo 29 Sept 2026
- R82.10 Take 40 · from 10 Aug 2026 to 29 Sept 2026
Source: Jumbo Hotfix Accumulator R82.10last verified by Patcharo 30 Sept 2026 at 00:17 UTC
R82
R82 Take 127 · since 22 Sept 2026
Vendor wording: “Each Jumbo Hotfix Accumulator is considered Recommended from the day of its release”
Policy: each newly released build is recommended from its release · stated 16 Sept 2026
Last build specifically declared as recommended: Take 122, on 10 Aug 2026 (kept as history)
History of the statement
- R82 Take 127 · current since 22 Sept 2026 · first read by Patcharo 29 Sept 2026
- R82 Take 122 · from 10 Aug 2026 to 29 Sept 2026
Source: Jumbo Hotfix Accumulator R82last verified by Patcharo 30 Sept 2026 at 00:17 UTC
R81.20
R81.20 Take 170 · since 22 Sept 2026
Vendor wording: “Each Jumbo Hotfix Accumulator is considered Recommended from the day of its release”
Policy: each newly released build is recommended from its release · stated 16 Sept 2026
Last build specifically declared as recommended: Take 161, on 10 Aug 2026 (kept as history)
History of the statement
- R81.20 Take 170 · current since 22 Sept 2026 · first read by Patcharo 29 Sept 2026
- R81.20 Take 161 · from 10 Aug 2026 to 29 Sept 2026
Source: Jumbo Hotfix Accumulator R81.20last verified by Patcharo 30 Sept 2026 at 00:17 UTC
R81.10
R81.10 Take 192 · since 22 Sept 2026
Vendor wording: “Each Jumbo Hotfix Accumulator is considered Recommended from the day of its release”
Policy: each newly released build is recommended from its release · stated 16 Sept 2026
Last build specifically declared as recommended: Take 187, on 21 Jun 2026 (kept as history)
Source: Jumbo Hotfix Accumulator R81.10last verified by Patcharo 30 Sept 2026 at 00:17 UTC
Support status of the releases
From the vendor's published life cycle policy.
| Product | Branch | Support | End of support |
|---|---|---|---|
| Quantum Security Gateway | R82.20 | Supported | 30 Sept 2030 |
| Quantum Security Management | R82.20 | Supported | 30 Sept 2030 |
| Quantum Security Gateway | R82.10 | Supported | 30 Jun 2030 |
| Quantum Security Management | R82.10 | Supported | 30 Jun 2030 |
| Quantum Security Gateway | R82 | Supported | 30 Apr 2029 |
| Quantum Security Management | R82 | Supported | 30 Apr 2029 |
| Quantum Security Gateway | R81.20 | Approaching end of support | 31 May 2027 |
| Quantum Security Management | R81.20 | Approaching end of support | 31 May 2027 |
| Quantum Security Gateway | R81.10 | End of life | 31 Mar 2026 |
| Quantum Security Management | R81.10 | End of life | 31 Mar 2026 |
| Quantum Security Gateway | R81 | End of life | 31 Oct 2024 |
| Quantum Security Management | R81 | End of life | 31 Oct 2024 |
| Quantum Security Gateway | R80.40 | End of life | 30 Apr 2024 |
| Quantum Security Management | R80.40 | End of life | 30 Apr 2024 |
| Quantum Security Gateway | R80.20 | End of life | 30 Sept 2022 |
| Quantum Security Management | R80.20 | End of life | 30 Sept 2022 |
| Quantum Security Gateway | R80.30 | End of life | 30 Sept 2022 |
| Quantum Security Management | R80.30 | End of life | 30 Sept 2022 |
| Quantum Security Gateway | R80 | End of life | 31 Jan 2022 |
| Quantum Security Management | R80 | End of life | 31 Jan 2022 |
| Quantum Security Gateway | R80.10 | End of life | 31 Jan 2022 |
| Quantum Security Management | R80.10 | End of life | 31 Jan 2022 |
| Quantum Security Gateway | R77.30 | End of life | 30 Sept 2019 |
| Quantum Security Management | R77.30 | End of life | 30 Sept 2019 |
| Quantum Security Gateway | R77 | End of life | 31 Aug 2017 |
| Quantum Security Management | R77 | End of life | 31 Aug 2017 |
| Quantum Security Gateway | R77.10 | End of life | 31 Aug 2017 |
| Quantum Security Management | R77.10 | End of life | 31 Aug 2017 |
| Quantum Security Gateway | R77.20 | End of life | 31 Aug 2017 |
| Quantum Security Management | R77.20 | End of life | 31 Aug 2017 |
| Quantum Security Gateway | R76 | End of life | 28 Feb 2017 |
| Quantum Security Management | R76 | End of life | 28 Feb 2017 |
| Quantum Security Gateway | R75.40 | End of life | 30 Apr 2016 |
| Quantum Security Management | R75.40 | End of life | 30 Apr 2016 |
| Quantum Security Gateway | R75.45 | End of life | 30 Apr 2016 |
| Quantum Security Management | R75.45 | End of life | 30 Apr 2016 |
| Quantum Security Gateway | R75.46 | End of life | 30 Apr 2016 |
| Quantum Security Management | R75.46 | End of life | 30 Apr 2016 |
| Quantum Security Gateway | R75.47 | End of life | 30 Apr 2016 |
| Quantum Security Management | R75.47 | End of life | 30 Apr 2016 |
| Quantum Security Gateway | R75.20 | End of life | 31 Aug 2015 |
| Quantum Security Management | R75.20 | End of life | 31 Aug 2015 |
| Quantum Security Gateway | R75.30 | End of life | 31 Aug 2015 |
| Quantum Security Management | R75.30 | End of life | 31 Aug 2015 |
| Quantum Security Gateway | R75 | End of life | 31 Jan 2015 |
| Quantum Security Management | R75 | End of life | 31 Jan 2015 |
| Quantum Security Gateway | R75.10 | End of life | 31 Jan 2015 |
| Quantum Security Management | R75.10 | End of life | 31 Jan 2015 |
What Patcharo does with it
In the application, each asset and each watch is compared with these statements: on the recommendation, recommendation available, ahead of it, or not comparable when the installed value is not recognised in trusted data. A change of the recommended release or of a branch's recommended Take raises an alert. The comparison never changes a vulnerability status, which comes from the security advisories only.
Sources
The recommended version and the JHF policy come from sk95746; each branch's Takes from its Jumbo Hotfix Accumulator page on sc1.checkpoint.com; support dates from the Check Point support life cycle policy. Retrieval and verification dates are shown on each statement.