Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Reach exposed Meraki/Gateway interface
  2. Exploit
    Send crafted malformed input
  3. Execution
    Bypass improper input validation (CWE-20)
  4. Impact
    Tamper device integrity, degrade service

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
Exploitation Conditions

Per the supplied CVSS vector (AV:N/AC:L/PR:N/UI:N) exploitation requires only network reachability to an affected Cisco Meraki MR/MV/MX or Campus Gateway device, with no authentication, no user interaction, and low complexity against default configurations. Limiting factors: the advisory is a bundled internal-hardening release covering multiple CWE-20 input-validation issues without naming the specific vulnerable feature, protocol, or interface, so the exact exposed service and whether it is reachable from untrusted networks versus management-only paths cannot be confirmed from available data; affected-version boundaries are not stated in the input and should be taken from the Cisco advisory.

Impact

Signals are moderately strong but partly opaque. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated flaw, which normally implies broad exposure, and the 8.2 score is driven by high integrity impact (I:H) plus low availability impact (A:L) with no confidentiality impact (C:N). No EPSS score, no CISA KEV listing, and no public POC were provided, so exploitation probability signals are entirely absent - there is no public exploit identified at time of analysis. Note a data conflict: the 'Information Disclosure' tag implies confidentiality loss, yet the CVSS vector explicitly sets C:N - verify the true impact with Cisco, as the tag and vector disagree. The description is also a generic 'software hardening' bundle covering multiple internally-discovered CWE-20 input-validation issues rather than one characterized bug, so the real-world triggerability of the network/unauthenticated path cannot be independently confirmed from the input. Overall this is a credible medium-to-high priority for Meraki/Campus Gateway operators given the ubiquity of these appliances and the unauthenticated network vector, but the absence of exploitation evidence and the vague, bundled disclosure argue for patch-on-cycle rather than emergency response.

Exploit ScenarioDerived

A remote, unauthenticated attacker who can reach the management or data-plane interface of an affected Cisco Meraki (MR/MV/MX) or Campus Gateway device sends crafted input that bypasses improper input validation (CWE-20), tampering with device integrity and causing partial service degradation. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, no credentials, user interaction, or complex preconditions are required per the stated metrics. No public exploit code has been identified, and the bundled hardening advisory provides no per-vulnerability technical detail.

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

Improper input validation in Cisco Meraki MR wireless access point, MV camera, and MX security appliance firmware - together with Cisco Campus Gateway Software - allows unauthenticated remote attackers to feed crafted input that the affected device fails to validate, producing a high integrity impact and a limited availability impact (C:N/I:H/A:L) under the assessed CVSS 3.1 vector. The issue is one of a set of CWE-20 weaknesses remediated in a single Cisco internal-hardening firmware release, so the specific vulnerable feature, protocol, or interface is not named and the affected version boundaries must be taken from the Cisco advisory. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV); note that the 'Information Disclosure' tag does not align with the assessed vector, which shows no confidentiality impact.

RemediationAI

The primary fix is the vendor hardening release documented in Cisco Security Advisory cisco-sa-hardening-meraki-os-drbEX9GH (https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-hardening-meraki-os-drbEX9GH); exact fixed firmware versions are not present in the supplied data and must be read from that advisory before upgrading, since all CPE version fields are wildcards. Cisco Meraki MR, MV, and MX devices are cloud-managed and are typically brought to the remediated build through scheduled firmware upgrades in the Meraki dashboard (with manual/on-demand upgrade scheduling available), while Campus Gateway Software follows the standard Cisco software upgrade path for that platform. Until the fixed builds are confirmed and deployed, and because the advisory does not name the vulnerable feature, protocol, or interface, no targeted feature-disable workaround can be prescribed; the practical compensating controls are infrastructure-level - restrict reachability of device management interfaces and any exposed device services to trusted management VLANs by tightening ACLs, firewalls, and segmentation so that only administrative networks can reach affected devices, and monitor for anomalous configuration changes consistent with the integrity impact described by the vector. The trade-offs are that over-broad blocking of a Meraki device's outbound paths can break dashboard management, cloud connectivity, and remote troubleshooting, and that the affected devices also pass production traffic, so segmentation rules must be scoped to management-plane ports rather than the data plane. If the advisory ultimately identifies the vulnerable interface, prefer the vendor-released fixed firmware over any partial mitigation.

Affected VersionsENISA

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

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

The affected products are cloud-managed Cisco networking platforms: Meraki MR access points, MV cameras, and MX security/SD-WAN appliances, which are all provisioned and monitored through the Meraki dashboard, plus Cisco Campus Gateway Software. The root cause class is CWE-20 (Improper Input Validation), used here as a pillar grouping several internally discovered weaknesses rather than a single precisely scoped flaw, which is characteristic of a vendor hardening release that fixes multiple validation defects in one firmware drop. Per the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L, the vulnerable code path is reachable over the network with no authentication, no user interaction, and low complexity against default configurations, with the demonstrated impact falling on integrity (I:H) and, secondarily, availability (A:L). The CPE data confirms the affected surface spans four distinct product families (cpe:2.3:a:cisco:cisco_campus_gateway_software, cisco:cisco_meraki_mr_wireless_access_points_software, cisco:cisco_meraki_mv_firmware, cisco:cisco_meraki_mx_firmware), all recorded with wildcard versions, so the precise service that accepts the unvalidated input - and whether it is exposed to untrusted networks or only to management paths - cannot be confirmed from the available data.

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 HIGH
NVD 8.2 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
vuln.today AI 8.2 HIGH

Retained network unauthenticated low-complexity vector from the input as the description gives no basis to narrow AV/PR; integrity high and availability low with no confidentiality impact.

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

Primary rating from Vendor (cisco).

CVSS VectorNVD

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

DescriptionNVD

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-76468 are related to improper input validation that are grouped under the Common Weakness Enumeration (CWE) Pillar CWE-20.

Executive ViewAI

Why It Matters

Cisco Meraki MR wireless access points, MV cameras, MX security appliances, and Campus Gateway Software contain an improper input validation vulnerability that could allow remote attackers to compromise data integrity and cause limited availability disruptions. These devices are often critical for network access, physical security, and perimeter defense, so successful exploitation could undermine trust in organizational systems and expose sensitive operations. With no vendor-released patch identified at time of analysis and no public exploit identified at time of analysis, leadership should prioritize risk mitigation and monitoring until a fix is released.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include network segmentation, restricting access to affected devices, and monitoring for anomalous traffic. Consult Cisco advisory for any specific workarounds.

Threat Intelligence Overview

EPSS Score
0.2%
Top 88% exploitable
Prevalence
High
Cisco Meraki MR/MV/MX and Campus Gateway are widely deployed enterprise networking appliances
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
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

41
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +41
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