Retrospective for 2026-08-04, compiled on 27 October 2026. The date identifies the day being analysed; source publication and revision dates are recorded below.
What this advisory changes in your environment
The starting point is CERTFR-2026-AVI-0965, published on 2026-08-04. Its scope includes Security Management, Multi-Domain Security Management. Reported consequences are remote code execution, security control bypass. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.
This case contains 6 version entries; CVE identifier count: 1. Track remediation by component: a successful overall update does not demonstrate that Security Management and Multi-Domain Security Management each received their respective fix.
Products and versions to examine
- Reference
- CERTFR-2026-AVI-0965
- Source first published
- 2026-08-04
- Latest source revision available for this day
- 2026-08-04
- Named components
- Security Management, Multi-Domain Security Management
- CVE identifiers
- CVE-2026-18574
| Component | Published condition |
|---|---|
| Security Management | R82.10 : < R82.10 Take 40 |
| Security Management | R82 : < R82 Take 122 |
| Multi-Domain Security Management | R82 : < R82 Take 122 |
| Multi-Domain Security Management | R81.20 : < R81.20 Take 161 |
| Security Management | R81.20 : < R81.20 Take 161 |
| Multi-Domain Security Management | R82.10 : < R82.10 Take 40 |
For Security Management, the published condition is “R82.10 : < R82.10 Take 40”. Compare the version actually loaded with that condition within its own release branch. A fix installed on another edition of Security Management does not close this case.
Mechanism and prerequisites
Code execution can give an attacker the permissions of the affected process. Check the service account and reachable network destinations. Component isolation can reduce lateral movement opportunities, but does not replace the fix.
For CERTFR-2026-AVI-0965, the retained documents do not provide a suitably dated primary CVE record to establish this case’s prerequisites. Required authentication, user interaction and active exploitation therefore remain unestablished here; they are not inferred from Security Management or the risk category alone.
Choose the appropriate intervention
- Locate Security Management instances, running releases and service owners. Record condition R82.10 : < R82.10 Take 40 in the ticket alongside reference CERTFR-2026-AVI-0965.
- Compare the installed branch with the vendor’s Security Management release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
- After changing Security Management, capture the loaded version again and verify the workflow below. Any exception needs an owner, an exposure-reduction measure and an expiry date.
Verify the fix in a real workflow
Validation scenario to adapt for Security Management: For Security Management, test an authorised business flow from each zone reaching the service and confirm management restrictions. If a redundant pair exists, verify both nodes and rule persistence after failover during a planned maintenance window. This is a proposed defensive check, not a claim that testing was performed against third-party systems.
Limit of case CERTFR-2026-AVI-0965: this analysis replaces neither vendor prerequisites nor investigation of your logs. Only documented versions are reproduced; no attack date or victim is invented.
Questions specific to this case
Which condition should be checked for Security Management?
Advisory CERTFR-2026-AVI-0965 states: Security Management — R82.10 : < R82.10 Take 40. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.
Why not use one fix for Security Management and Multi-Domain Security Management?
CERTFR-2026-AVI-0965 distinguishes these components within a scope containing 6 entries. Match each branch to its own update documentation and functional check.
What is still needed to assess Security Management exposure?
For Security Management, establish the running version, the path to the component and process permissions. The sources retained for CERTFR-2026-AVI-0965 do not establish every prerequisite or active exploitation.
Sources and related reading
Practical guide : Software inventory: prepare for end of support
Explore the decision addressed in this case
Complete source advisory inventory
The article table may be an extract. These lists contain every affected-system entry and CVE in the specified advisory revision. They are not an inventory of your assets and do not map every CVE to every product.
Official source · CERTFR-2026-AVI-0965
Advisory revision : · Checked on :
Affected systems · 6
Original French wording is retained to avoid ambiguous translations of version conditions.
- Security Management versions R82.10 antérieures à R82.10 Take 40
- Security Management versions R82 antérieures à R82 Take 122
- Multi-Domain Security Management versions R82 antérieures à R82 Take 122
- Multi-Domain Security Management versions R81.20 antérieures à R81.20 Take 161
- Security Management versions R81.20 antérieures à R81.20 Take 161
- Multi-Domain Security Management versions R82.10 antérieures à R82.10 Take 40
Historical note from this revision: check current patch availability with the vendor before acting.
Check Point indique que les versions obsolètes R80, R80.10, R80.20, R80.30, R80.40, R81 et R81.10 sont également affectées.