CVE-2025-20155
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 the bootstrap loading of Cisco IOS XE Software could allow an authenticated, local attacker to write arbitrary files to an affected system. This vulnerability is due to insufficient input validation of the bootstrap file that is read by the system software when a device is first deployed in SD-WAN mode or when an administrator configures SD-Routing on the device. An attacker could exploit this vulnerability by modifying a bootstrap file generated by Cisco Catalyst SD-WAN Manager, loading it into the device flash, and then either reloading the device in a green field deployment in SD-WAN mode or configuring the device with SD-Routing. A successful exploit could allow the attacker to perform arbitrary file writes to the underlying operating system.
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 exists in the bootstrap loading mechanism of Cisco IOS XE Software. When a device is deployed in SD-WAN mode (green field) or configured with SD-Routing, it reads a bootstrap file generated by Cisco Catalyst SD-WAN Manager from device flash. Due to insufficient input validation of this bootstrap file, an authenticated local attacker who can modify the bootstrap file can achieve arbitrary file writes to the underlying operating system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 17.9.4= 17.9.4a= 17.9.5= 17.9.5a= 17.9.5b= 17.9.5e= 17.9.5f= 17.9.6= 17.9.6a= 17.11.99sw= 17.12.1= 17.12.1aCVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/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 installed IOS XE versionExecute 'show version' on the device CLI and locate the IOS XE release string (for example, 17.9.5 or 17.12.1)Affected if The version matches any of these: 17.9.4, 17.9.4a, 17.9.5, 17.9.5a, 17.9.5b, 17.9.5e, 17.9.5f, 17.9.6, 17.9.6a, 17.11.99sw, 17.12.1, or 17.12.1a
-
Determine if device is in SD-WAN modeRun 'show sdwan version' or check the boot variable with 'show boot' to see if the device was deployed via SD-WAN zero-touch provisioning (green field)Affected if The device shows as SD-WAN enabled or was deployed in SD-WAN mode
-
Check for SD-Routing configurationRun 'show running-config | include sd-routing' or look for SD-Routing related configuration in the device configAffected if SD-Routing feature is configured on the device
-
Locate bootstrap files on flash storageExecute 'dir flash:' or 'show flash:' to list files on the device flash. Look for files with bootstrap-related naming such as .bootstrap extensions or sdwan_bootstrap filesAffected if Bootstrap files generated by Cisco Catalyst SD-WAN Manager exist on the device flash
A device is affected if it runs any of the listed IOS XE versions AND is deployed in SD-WAN mode (green field) or has SD-Routing configured, with a bootstrap file present on flash that could be modified by an authenticated local attacker.
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.
dbcve · scopedRestrict physical and administrative access to devices to prevent unauthorized modification of bootstrap files. Validate bootstrap file integrity through Cisco-provided mechanisms before loading. Monitor for unauthorized changes to flash storage. Apply Cisco IOS XE patches when released.
IOS XE 17.9.6 or later (17.9.x train)
- 1. Verify current IOS XE version by running 'show version' on the device
- 2. Confirm the device is running one of the affected versions: 17.9.4, 17.9.4a, 17.9.5, or 17.9.5a
- 3. Download the fixed IOS XE release (17.9.6 or later) from Cisco Software Central (software.cisco.com)
- 4. Back up the current device configuration using 'copy running-config tftp:' or 'write memory'
- 5. If using SD-WAN, also back up the bootstrap configuration files from flash
- 6. Upgrade the IOS XE software image using 'software install file <image> new' command
- 7. After upgrade, verify the new version is running with 'show version'
- 8. Reload the device if required by the upgrade process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20155 — 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-2025-20155 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