CVE-2026-20115
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability in Cisco IOS XE Software for Cisco Meraki could allow a remote, unauthenticated attacker to view confidential device information. This vulnerability is due to a device configuration upload being performed over an insecure tunnel. An attacker could exploit this vulnerability by conducting an on-path attack between the affected device and the Cisco Meraki Dashboard. A successful exploit could allow the attacker to view sensitive device configuration information.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis vulnerability in Cisco IOS XE Software for Cisco Meraki allows a remote, unauthenticated attacker to view confidential device configuration information. The root cause is that device configuration uploads are performed over an insecure tunnel, enabling an on-path (man-in-the-middle) attack between the affected device and the Cisco Meraki Dashboard.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device OS and versionRun 'show version' or check the device management interface to confirm the device is running Cisco IOS XE Software for Cisco MerakiAffected if The device is running Cisco IOS XE Software for Cisco Meraki (any version)
-
Verify Meraki Dashboard integration is enabledCheck the device configuration for Meraki cloud management settings, typically via 'show meraki' commands or by reviewing the device registration status in the Meraki DashboardAffected if The device is registered to and communicating with the Cisco Meraki Dashboard for configuration management
-
Confirm configuration upload functionality is activeReview device logs or network captures for evidence of periodic configuration uploads to Meraki cloud infrastructure (typically toward dashboard.meraki.com or api.meraki.com)Affected if Configuration synchronization between the device and Meraki Dashboard is active
-
Assess network exposure to on-path attacksExamine whether the device communicates with Meraki cloud services over unencrypted or insufficiently protected network paths, especially when traversing untrusted networksAffected if Device-to-Dashboard traffic can be intercepted by an on-path attacker (traffic crosses untrusted network segments without VPN or encryption protection)
A user is affected if their device runs Cisco IOS XE Software for Cisco Meraki with active Meraki Dashboard integration where configuration uploads traverse an insecure network path susceptible to man-in-the-middle interception.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply Cisco-provided software updates for IOS XE when available. In the interim, implement network segmentation to reduce exposure and monitor for suspicious traffic patterns between devices and the Meraki Dashboard.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20115 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-20115 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data