Skip to main content

Cisco Meraki Firmware EUVDEUVD-2026-94479

| CVE-2026-76470 HIGH
Incorrect Calculation (CWE-682)
2026-10-07 cisco GHSA-c56x-q3cx-9pww
8.8
CVSS 3.1 · Vendor: cisco
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain foothold on adjacent network segment
  2. Delivery
    Send crafted packets to Meraki/Gateway device
  3. Exploit
    Trigger incorrect-calculation (CWE-682) flaw
  4. Execution
    Corrupt state or execute unintended logic
  5. Impact
    Compromise device confidentiality/integrity/availability

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Calculation correctness
Exploitation Conditions

Exploitation requires the attacker to be on an adjacent network (AV:A) - i.e., the same local/Layer-2 broadcast domain, management VLAN, or directly connected network segment as a vulnerable Cisco Meraki MR wireless AP, MV camera, MX security appliance, or Campus Gateway running the affected software; it is NOT exploitable from an arbitrary remote internet host. No authentication (PR:N) and no user interaction (UI:N) are required, and attack complexity is low (AC:L). The primary LIMITING factor is the adjacency requirement, which confines exploitation to attackers who have already achieved local network presence; the generic advisory text does not name a specific feature, protocol, or non-default configuration, so no additional configuration prerequisite can be confirmed from the available data.

Impact

Signals are mixed and lean toward moderate real-world urgency despite a high CVSS base score of 8.8. The CVSS vector (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) indicates an adjacent-network, low-complexity, unauthenticated attack with full confidentiality, integrity, and availability impact - serious in principle, but the AV:A (Adjacent) metric meaningfully limits exposure versus a network-routable (AV:N) flaw, since the attacker must already have a foothold on the same Layer-2/adjacent segment. No EPSS score, CISA KEV listing, or POC was provided in the input, so exploitation probability cannot be quantified and there is no public exploit identified at time of analysis. Crucially, this CVE originates from Cisco's own internal proactive security review and groups MULTIPLE internally discovered vulnerabilities under CWE-682 (Incorrect Calculation, a Pillar-level weakness) - the description provides no specific vulnerable component, trigger, or exploitation mechanics. SSVC framework data is absent. Net assessment: this is a legitimate patch-worthy issue for Meraki/Campus Gateway operators given the high impact, but the adjacent-only vector, internal (not external) discovery, and absence of any exploitation evidence suggest it is not an emergency compared to actively-exploited network-facing CVEs. The 'Information Disclosure' tag conflicts with the C:H/I:H/A:H vector, which implies far more than disclosure - verify scope with the Cisco advisory.

Exploit ScenarioDerived

An attacker who has gained a position on the same adjacent/local network segment as a vulnerable Meraki MR/MV/MX device or Campus Gateway (e.g., via a compromised adjacent host or rogue device on the LAN/management VLAN) sends crafted traffic that triggers the incorrect-calculation flaw, requiring no authentication or user interaction. Successful exploitation could compromise confidentiality, integrity, and availability of the affected appliance. No public proof-of-concept or exploit code was identified in the provided data.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

Incorrect-calculation flaws in Cisco's hardening release for Meraki MR wireless access points, MV cameras, MX security appliances, and Campus Gateway software allow an unauthenticated attacker on an adjacent network segment to achieve high impact to confidentiality, integrity, and availability (CVSS 8.8). Because the vector is AV:A/AC:L/PR:N/UI:N, exploitation requires the attacker to already sit in the same Layer-2 broadcast domain, management VLAN, or directly connected segment as the target device - it is not reachable from an arbitrary internet host, and that adjacency requirement is the principal limiting factor. No public exploit identified at time of analysis, and Cisco states the issues were discovered through its own proactive internal security review rather than through exploitation, so real-world urgency is moderate despite the high base score.

RemediationAI

Cisco's hardening release for these internally discovered issues is documented in the vendor advisory at https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-hardening-meraki-os-drbEX9GH - patch available per vendor advisory, with no exact fixed version number present in the supplied data, so confirm the correct target release per platform from the advisory before upgrading. Apply that release to every affected Cisco Meraki MR access point, MV camera, MX security appliance, and Campus Gateway; because Meraki hardware is cloud-managed, upgrades are typically staged through the dashboard, but verify the firmware actually applied since scheduled upgrade windows can leave devices running the vulnerable build. If immediate upgrade is not possible, all meaningful compensating controls target the AV:A adjacency requirement: segment management and device VLANs so untrusted hosts cannot share a broadcast domain with the devices, disable unused switch ports and apply port security or 802.1X/NAC to block unauthorized Layer-2 access, limit wireless client onboarding to trusted devices, and monitor for anomalous local traffic directed at device management interfaces. These measures reduce exposure but do not eliminate the flaw, and they carry operational trade-offs - tighter segmentation and NAC can complicate guest access, camera onboarding, and legitimate provisioning workflows.

Affected VersionsENISA

Cisco Meraki MV Firmware 3.13
Cisco Meraki MV Firmware 2.1
Cisco Meraki MX Firmware 17.3
Cisco Meraki MV Firmware 3.1
Cisco Meraki MV Firmware 3.0
Cisco Meraki MV Firmware 3.24
Cisco Meraki MX Firmware MX 18.211.2
Cisco Meraki MR Wireless Access Points Software MR 33.1.2
Cisco Meraki MV Firmware 4.17
Cisco Meraki MV Firmware 4.5
Cisco Meraki MV Firmware 5.2
Cisco Meraki MV Firmware 6.1.1
Cisco Meraki MV Firmware MV 7.3.2
Cisco Meraki MV Firmware 6.0.1
Cisco Meraki MR Wireless Access Points Software MR 33.1.1
Cisco Meraki MX Firmware 16.6
Cisco Meraki MV Firmware 4.7
Cisco Meraki MX Firmware MX 26.2.2
Cisco Meraki MV Firmware 4.20
Cisco Meraki MV Firmware 3.30
Cisco Meraki MV Firmware 4.4
Cisco Meraki MX Firmware 18.1
Cisco Meraki MV Firmware 6.2.2
Cisco Meraki MR Wireless Access Points Software MR 32.1.7
Cisco Meraki MX Firmware MX 26.1.4
Cisco Meraki MV Firmware 4.1
Cisco Meraki MV Firmware 3.10
Cisco Meraki MV Firmware 3.4
Cisco Meraki MX Firmware MX 26.2.1
Cisco Meraki MV Firmware 3.16
Cisco Meraki MV Firmware 2.2
Cisco Meraki MX Firmware 16.4
Cisco Meraki MV Firmware 4.13
Cisco Meraki MV Firmware MV 7.3
Cisco Meraki MV Firmware 4.15
Cisco Meraki MV Firmware 3.22
Cisco Meraki MV Firmware 3.18
Cisco Meraki MV Firmware 3.36
Cisco Meraki MV Firmware 3.21
Cisco Meraki MV Firmware 6.0
Cisco Meraki MV Firmware MV 7.2.1
Cisco Meraki MV Firmware 6.3
Cisco Meraki MV Firmware 6.2
Cisco Meraki MV Firmware MV 7.3.1
Cisco Meraki MV Firmware 3.28
Cisco Meraki MV Firmware 5.1
Cisco Meraki MX Firmware 18.2
Cisco Meraki MV Firmware 5.4.1
Cisco Meraki MV Firmware 4.12
Cisco Meraki MV Firmware 3.26
Cisco Meraki MV Firmware 2.0
Cisco Meraki MX Firmware 19.1
Cisco Meraki MV Firmware 5.0
Cisco Meraki MV Firmware 3.9
Cisco Meraki MX Firmware MX 26.1.5
Cisco Meraki MV Firmware 4.18
Cisco Meraki MV Firmware 3.5
Cisco Meraki MV Firmware 5.6.1
Cisco Meraki MV Firmware 3.11
Cisco Meraki MV Firmware 3.19
Cisco Meraki MV Firmware 3.12
Cisco Meraki MV Firmware 3.31
Cisco Meraki MV Firmware 4.16
Cisco Meraki MR Wireless Access Points Software MR 30.6
Cisco Meraki MV Firmware 5.5
Cisco Meraki MV Firmware 3.33
Cisco Meraki MV Firmware 3.14
Cisco Meraki MV Firmware 4.0
Cisco Meraki MV Firmware 6.1.2
Cisco Meraki MV Firmware 4.8
Cisco Meraki MX Firmware 16.5
Cisco Meraki MV Firmware 5.6.2
Cisco Meraki MV Firmware 3.17
Cisco Meraki MV Firmware 4.11
Cisco Meraki MV Firmware 4.3
Cisco Meraki MX Firmware 17.9
Cisco Meraki MR Wireless Access Points Software MR 32.2.4
Cisco Meraki MV Firmware 3.34
Cisco Meraki MV Firmware 4.9
Cisco Meraki MV Firmware 3.32
Cisco Meraki MV Firmware 5.5.1
Cisco Meraki MX Firmware 17.7
Cisco Meraki MX Firmware MX 19.2.8
Cisco Meraki MV Firmware 5.6
Cisco Meraki MV Firmware 4.10
Cisco Meraki MV Firmware 3.7
Cisco Meraki MX Firmware 16.3
Cisco Meraki MV Firmware 3.29
Cisco Meraki MX Firmware MX 26.1.6
Cisco Meraki MX Firmware 16.2
Cisco Meraki MV Firmware 3.35
Cisco Meraki MV Firmware 5.4
Cisco Meraki MV Firmware 3.15
Cisco Meraki MV Firmware 6.2.1
Cisco Meraki MV Firmware 3.6
Cisco Meraki MV Firmware 3.20
Cisco Meraki MX Firmware 17.10
Cisco Meraki MV Firmware MV 7.2.2
Cisco Meraki MV Firmware 4.2
Cisco Meraki MV Firmware 5.3
Cisco Meraki MV Firmware 6.1
Cisco Meraki MR Wireless Access Points Software MR 32.2.3
Cisco Meraki MV Firmware 3.8
Cisco Meraki MV Firmware 4.14
Cisco Meraki MV Firmware 4.18.1
Cisco Meraki MV Firmware 3.23
Cisco Meraki MV Firmware 4.19
Cisco Meraki MV Firmware 3.25
Cisco Campus Gateway Software CG 33.1.3
Cisco Meraki MV Firmware 3.27
Cisco Meraki MV Firmware 3.3
Cisco Meraki MV Firmware 3.2
Cisco Meraki MV Firmware 6.3.2
Cisco Meraki MV Firmware 4.6
Cisco Meraki MV Firmware 6.0.2
Cisco Meraki MX Firmware 17.8
Cisco Meraki MX Firmware 17.6

Affected Packages

euvd cisco_campus_gateway_software_cg no fix
euvd cisco_meraki_mr_wireless_access_points_software_mr no fix
euvd cisco_meraki_mv_firmware no fix
euvd cisco_meraki_mv_firmware_mv no fix
euvd cisco_meraki_mx_firmware no fix
euvd cisco_meraki_mx_firmware_mx no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 6 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-682 (Incorrect Calculation) is a pillar weakness class covering arithmetic and logic errors such as integer overflow or underflow, off-by-one sizing, incorrect length or index computation, and faulty protocol-field math - errors that typically surface during buffer allocation, packet parsing, or memory handling. The affected code paths live in the operating software of Cisco Meraki MR access points, MV cameras, MX security appliances, and Cisco Campus Gateway software, which means the flaws are reachable from the local network layer those devices service. The assessed vector AV:A/AC:L/PR:N/UI:N/S:U with C:H/I:H/A:H describes a low-complexity, unauthenticated attack launched from an adjacent segment that yields broad impact on the device itself rather than a credential-gated privilege escalation. Cisco packages the findings from its internal review into a single hardening release, and the available advisory text does not name the specific feature, protocol, or non-default configuration involved, so no additional precondition can be confirmed; note also that the accompanying intelligence tag labels the class as Information Disclosure, which is narrower than the assessed confidentiality, integrity, and availability impact.

Know when Cisco Campus Gateway Software gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (cisco) PRIMARY 8.8 HIGH
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Adjacent vector and unauthenticated low-complexity access per Cisco's vector; retained C/I/A:H as the description's bundled CWE-682 flaws and 8.8 score indicate full device compromise.

3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (cisco).

CVSS VectorVendor: cisco

Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco networking engineering team has conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities.

The vulnerabilities tracked by CVE-2026-76470 are related to incorrect calculation issues that are grouped under the Common Weakness Enumeration (CWE) Pillar CWE-682.

Executive ViewAI

Why It Matters

Cisco's Meraki MR access points, MV cameras, MX security appliances, and Campus Gateway software are affected by calculation flaws that let an attacker who already has a foothold on the same network segment degrade or disrupt the confidentiality, integrity, and availability of these devices. Because the affected products are the connectivity and physical-security backbone of branch, retail, and campus environments, a successful attack could interrupt wireless and wired access, cloud-managed device control, and video surveillance coverage at any site running unpatched hardware. No vendor patch is currently available, though no public exploit has been identified at time of analysis, so leadership should treat this as a near-term exposure-management and network-segmentation priority rather than an active incident.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict Layer-2 adjacency to trusted hosts, place management interfaces on a dedicated segmented VLAN reachable only from hardened admin systems, enforce 802.1X/NAC on access ports, disable unused switch ports, monitor adjacent-segment traffic for anomalies, and pursue Cisco TAC for workaround guidance.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
High
Cisco Meraki MR/MX/MV are widely deployed enterprise networking/wireless appliances
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy