Affects Cisco networking/Meraki OS—core enterprise networking infrastructure widely deployed; high-severity (CVSS 8.8) fix should be applied broadly.
CVE-2026-76470
Cisco Meraki hardening fixes multiple calculation-flaw vulnerabilities (CWE-682).
Is CVE-2026-76470 being exploited?
Not confirmed. CVE-2026-76470 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-76470?
CVE-2026-76470 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-76470?
Yes. A fix has been recorded for CVE-2026-76470. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76470 affect?
CVE-2026-76470 affects Cisco Meraki OS, Cisco network appliances / Meraki-managed devices. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76470?
Apply Cisco Meraki OS hardening update immediately after testing.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Calculation/logic flaws may allow bypass of checks, privilege escalation or service disruption on Cisco/Meraki network devices.
Patch when possible
- affectedCG 33.1.3
- affectedMR 33.1.2
- affectedMR 30.6
- affectedMR 32.1.7
- affectedMR 32.2.3
- affectedMR 32.2.4
- affectedMR 33.1.1
- affected4.20
- affected5.0
- affected5.1
- affected5.2
- affected5.3
- affected5.4
- affected5.4.1
- affected5.5
- affected5.5.1
- affected5.6
- affected5.6.1
- affected6.0
- affected6.0.1
- affected5.6.2
- affected6.0.2
- affected6.1
- affected6.1.1
- affected6.1.2
- affected6.2
- affected6.2.1
- affected6.2.2
- affected6.3
- affected6.3.2
- affected2.0
- affected2.1
- affected2.2
- affected3.0
- affected3.1
- affected3.2
- affected3.3
- affected3.4
- affected3.5
- affected3.6
- affected3.7
- affected3.8
- affected3.9
- affected3.10
- affected3.11
- affected3.12
- affected3.13
- affected3.14
- affected3.15
- affected3.16
- affected3.17
- affected3.18
- affected3.19
- affected3.20
- affected3.21
- affected3.22
- affected3.23
- affected3.24
- affected3.25
- affected3.26
- affected3.27
- affected3.28
- affected3.29
- affected3.30
- affected3.31
- affected3.32
- affected3.33
- affected3.34
- affected3.35
- affected3.36
- affected4.0
- affected4.1
- affected4.2
- affected4.3
- affected4.4
- affected4.5
- affected4.6
- affected4.7
- affected4.8
- affected4.9
- affected4.10
- affected4.11
- affected4.12
- affected4.13
- affected4.14
- affected4.15
- affected4.16
- affected4.17
- affected4.18
- affected4.18.1
- affected4.19
- affectedMV 7.3
- affectedMV 7.3.1
- affectedMV 7.3.2
- affectedMV 7.2.1
- affectedMV 7.2.2
- affected16.2
- affected16.3
- affected16.4
- affected16.5
- affected16.6
- affected17.3
- affected17.6
- affected17.7
- affected17.8
- affected17.9
- affected17.10
- affected18.1
- affected18.2
- affected19.1
- affectedMX 18.211.2
- affectedMX 26.2.1
- affectedMX 19.2.8
- affectedMX 26.2.2
- affectedMX 26.1.4
- affectedMX 26.1.5
- affectedMX 26.1.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.