Retrospective for 2026-06-15, 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-0750, published on 2026-06-15. Its scope includes Private 5G Management Dashboard, Airwave. Reported consequences are denial of service, remote code execution. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.
This case contains 2 version entries; CVE identifier count: 1. Track remediation by component: a successful overall update does not demonstrate that Private 5G Management Dashboard and Airwave each received their respective fix.
Products and versions to examine
- Reference
- CERTFR-2026-AVI-0750
- Source first published
- 2026-06-15
- Latest source revision available for this day
- 2026-06-15
- Named components
- Private 5G Management Dashboard, Airwave
- CVE identifiers
- CVE-2026-42945
| Component | Published condition |
|---|---|
| Private 5G Management Dashboard | < 1.25.2.2 |
| Airwave | < 8.3.0.7 |
For Private 5G Management Dashboard, the published condition is “< 1.25.2.2”. Compare the version actually loaded with that condition within its own release branch. A fix installed on another edition of Private 5G Management Dashboard, Airwave 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-0750, 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 Private 5G Management Dashboard, Airwave or the risk category alone.
Choose the appropriate intervention
- Locate Private 5G Management Dashboard instances, running releases and service owners. Record condition < 1.25.2.2 in the ticket alongside reference CERTFR-2026-AVI-0750.
- Compare the installed branch with the vendor’s Private 5G Management Dashboard release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
- After changing Private 5G Management Dashboard, 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 Private 5G Management Dashboard, Airwave: For Private 5G Management Dashboard, 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-0750: 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 Private 5G Management Dashboard?
Advisory CERTFR-2026-AVI-0750 states: Private 5G Management Dashboard — < 1.25.2.2. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.
Why not use one fix for Private 5G Management Dashboard and Airwave?
CERTFR-2026-AVI-0750 distinguishes these components within a scope containing 2 entries. Match each branch to its own update documentation and functional check.
What is still needed to assess Private 5G Management Dashboard, Airwave exposure?
For Private 5G Management Dashboard, Airwave, establish the running version, the path to the component and process permissions. The sources retained for CERTFR-2026-AVI-0750 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-0750
Advisory revision : · Checked on :
Affected systems · 2
Original French wording is retained to avoid ambiguous translations of version conditions.
- Private 5G Management Dashboard versions antérieures à 1.25.2.2
- Airwave versions antérieures à 8.3.0.7
Historical note from this revision: check current patch availability with the vendor before acting.
L'éditeur indique que ces versions correctives seront disponibles en juillet.