# CVE-2025-20143: Cisco IOS XR Software Secure Boot Bypass Vulnerability

> Authenticated local attackers with root privileges can bypass Secure Boot to load unverified software on Cisco IOS XR devices.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-2w36-grgh-xprc

## What is CVE-2025-20143?

CVE-2025-20143 is a medium-severity vulnerability in Cisco Ios Xr, published on 12 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the boot process of Cisco IOS XR Software could allow an authenticated, local attacker with high privileges to bypass the Secure Boot functionality and load unverified software on an affected device. To exploit this vulnerability, the attacker must have root-system privileges on the affected device.

This vulnerability is due to insufficient verification of modules in the software load process. An attacker could exploit this vulnerability by manipulating the loaded binaries to bypass some of the integrity checks that are performed during the booting process. A successful exploit could allow the attacker to control the boot configuration, which could enable them to bypass the requirement to run Cisco-signed images or alter the security properties of the running system.
Note: This vulnerability affects Cisco IOS XR Software, not the Secure Boot feature.
Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2025-20143?

It affects 1 product.


Products: Cisco Ios Xr.

## How do I fix CVE-2025-20143?

No fix has been published for CVE-2025-20143 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-20143 being exploited?

There is no known exploitation of CVE-2025-20143 in the wild and no public exploit code.

## Other vulnerabilities in Cisco Ios Xr

- [CVE-2020-3118](https://insights.sbomify.com/CVE-2020-3118/): Cisco IOS XR Software Discovery Protocol Format String (high 8.8, exploited in the wild)
- [CVE-2020-3569](https://insights.sbomify.com/CVE-2020-3569/): Cisco IOS XR Software DVMRP Memory Exhaustion (high 8.6, exploited in the wild)
- [CVE-2020-3566](https://insights.sbomify.com/CVE-2020-3566/): Cisco IOS XR Software DVMRP Memory Exhaustion (high 8.6, exploited in the wild)
- [CVE-2010-3035](https://insights.sbomify.com/CVE-2010-3035/): Cisco IOS XR Border Gateway Protocol (BGP) Denial-of-Service (high 7.5, exploited in the wild)
- [CVE-2022-20821](https://insights.sbomify.com/CVE-2022-20821/): Cisco IOS XR Open Port (medium 6.5, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-20143 and fix it if it is affected.

What it is: CVE-2025-20143 is a medium-severity vulnerability in Cisco Ios Xr, published on 12 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-20143 in the wild and no public exploit code.

Affected product: Cisco Ios Xr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-20143/ (Markdown: https://insights.sbomify.com/CVE-2025-20143/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-20143
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-20143
- OSV: https://osv.dev/vulnerability/CVE-2025-20143

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-20143/
Summaries are generated and may contain mistakes; the official description above is the record.