Retrospective for 2026-07-10, 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-0857, published on 2026-07-10. Its scope includes ONTAP 9 (formerly Clustered Data ONTAP). Reported consequences are denial of service, data integrity compromise. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.
This case focuses on ONTAP 9 (formerly Clustered Data ONTAP). Locate that edition in live installations, deployment images and actual dependencies, rather than treating every product from NetApp as equivalent.
Products and versions to examine
- Reference
- CERTFR-2026-AVI-0857
- Source first published
- 2026-07-10
- Latest source revision available for this day
- 2026-07-10
- Named components
- ONTAP 9 (formerly Clustered Data ONTAP)
- CVE identifiers
- CVE-2026-35547
Mechanism and prerequisites
Data modification can undermine decisions made from the system. Compare sensitive objects with a trusted reference and test recovery of a sample; an unverified backup is not proof of integrity.
The primary record CVE-2026-35547, published by freebsd, covers FreeBSD. The retained revision is dated 2026-05-01. Its scope is presented separately from the integrations and product groupings in CERTFR-2026-AVI-0857.
Choose the appropriate intervention
- Locate ONTAP 9 (formerly Clustered Data ONTAP) instances, running releases and service owners. Record condition Not specified in the retained source in the ticket alongside reference CERTFR-2026-AVI-0857.
- Compare the installed branch with the vendor’s ONTAP 9 (formerly Clustered Data ONTAP) release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
- After changing ONTAP 9 (formerly Clustered Data ONTAP), 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 ONTAP 9 (formerly Clustered Data ONTAP): For ONTAP 9 (formerly Clustered Data ONTAP), restore a synthetic dataset into an isolated environment and compare it with a reference. Check the management plane separately from the recovery path; a successful backup status does not prove service recovery. This is a proposed defensive check, not a claim that testing was performed against third-party systems.
Limit of case CERTFR-2026-AVI-0857: 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 ONTAP 9 (formerly Clustered Data ONTAP)?
Advisory CERTFR-2026-AVI-0857 states: ONTAP 9 (formerly Clustered Data ONTAP) — Not specified in the retained source. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.
What is still needed to assess ONTAP 9 (formerly Clustered Data ONTAP) exposure?
For ONTAP 9 (formerly Clustered Data ONTAP), establish the running version, the path to the component and process permissions. The sources retained for CERTFR-2026-AVI-0857 do not establish every prerequisite or active exploitation.
Sources and related reading
Practical guide : Test a backup restoration from copy to working service
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-0857
Advisory revision : · Checked on :
Affected systems · 2
Original French wording is retained to avoid ambiguous translations of version conditions.
- NetApp ONTAP 9 versions9 .13.x antérieures à 9.13.1P21
- NetApp ONTAP 9 versions9 .17.x antérieures à 9.17.1P9