# CVE-2025-32463: Sudo Inclusion of Functionality from Untrusted Control Sphere

> Local attackers can gain root access by exploiting the --chroot option to load a malicious nsswitch.conf from a user-controlled directory.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 29 Sep 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jun 2025
- **Updated:** 26 Feb 2026
- **Also known as:** AZL-64458, AZL-64464, BELL-CVE-2025-32463, DEBIAN-CVE-2025-32463, GHSA-695j-c63m-mvxc, UBUNTU-CVE-2025-32463

## What is CVE-2025-32463?

CVE-2025-32463 is a critical vulnerability in Canonical Ubuntu Linux, published on 30 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Sudo before 1.9.17p1 allows local users to obtain root access because /etc/nsswitch.conf from a user-controlled directory is used with the --chroot option.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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

It affects 8 products.


Products: Canonical Ubuntu Linux, Debian Debian Linux, Opensuse Leap, Redhat Enterprise Linux, Sudo Project Sudo, Suse Linux Enterprise Desktop, Suse Linux Enterprise Real Time, Suse Linux Enterprise Server for Sap.

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

Upgrade to a fixed version. US federal agencies must fix it by 20 Oct 2025.

## Is CVE-2025-32463 being exploited?

Yes. Attackers have exploited CVE-2025-32463 in the wild since at least 29 Sep 2025.

Public exploit code:

- Escalation of Privilege to the root through sudo binary with chroot option. CVE-2025-32463 (github_poc): https://github.com/pr0v3rbs/CVE-2025-32463_chwoot
- Local Privilege Escalation to Root via Sudo chroot in Linux (github_poc): https://github.com/kh4sh3i/CVE-2025-32463
- Privilege escalation to root using sudo chroot, NO NEED for gcc installed. (github_poc): https://github.com/MohamedKarrab/CVE-2025-32463
- CVE-2025-32463 Proof of concept (github_poc): https://github.com/K1tt3h/CVE-2025-32463-POC
- This CVE addresses a vulnerability in sudo versions 1.9.14 to 1.9.17, enabling unauthorized local privilege escalation to root access. (github_poc): https://github.com/1xPwn/CVE-2025-32463
- PoC for CVE-2025-32463 - Sudo chroot Elevation of Privilege Vulnerability (github_poc): https://github.com/mirchr/CVE-2025-32463-sudo-chwoot

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32463 is a critical vulnerability in Canonical Ubuntu Linux, published on 30 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-32463 in the wild since at least 29 Sep 2025.

Affected product: Canonical Ubuntu Linux. 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-32463/ (Markdown: https://insights.sbomify.com/CVE-2025-32463/index.md)
```

## Sources

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

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