# CVE-2025-32462: Missing authorization in Sudo

> Attackers can execute commands on unintended machines if sudoers restricts hosts incorrectly, leading to privilege escalation.

- **Severity:** Low 2.8 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jun 2025
- **Updated:** 14 Jul 2026
- **Also known as:** ALSA-2025:10110, ALSA-2025:9978, AZL-64449, AZL-64461, BELL-CVE-2025-32462, CLSA-2025-1751893905, CLSA-2025-1751895848, CLSA-2025-1751900234, CLSA-2025-1751913242, CLSA-2025-1751913478, CLSA-2025-1751913630, CLSA-2025-1752746954, CLSA-2025-1753799090, CLSA-2025-1753799668, CLSA-2025-1753799801, DEBIAN-CVE-2025-32462, DLA-4235-1, DSA-5954-1, ECHO-7021-c433-f22c, GHSA-c5x2-97hm-x895, OESA-2025-1733, OESA-2025-1734, OESA-2025-1737, RHSA-2025:10110, RHSA-2025:10383, RHSA-2025:10518, RHSA-2025:10520, RHSA-2025:10707, RHSA-2025:10779, RHSA-2025:10835, RHSA-2025:10836, RHSA-2025:10871, RHSA-2025:9978, RLSA-2025:10110, RLSA-2025:9978, ROOT-OS-UBUNTU-2004-CVE-2025-32462, SUSE-SU-2025:02174-1, SUSE-SU-2025:02175-1, SUSE-SU-2025:02178-1, SUSE-SU-2025:02179-1, UBUNTU-CVE-2025-32462, USN-7604-2

## What is CVE-2025-32462?

CVE-2025-32462 is a low-severity missing authorization vulnerability in Sudo, 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, when used with a sudoers file that specifies a host that is neither the current host nor ALL, allows listed users to execute commands on unintended machines.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sudo` | AlmaLinux:8 | All versions | 1.9.5p2-1.el8_10.1 |
| `sudo` | AlmaLinux:9 | All versions | 1.9.5p2-10.el9_6.1 |
| `sudo-python-plugin` | AlmaLinux:9 | All versions | 1.9.5p2-10.el9_6.1 |
| `sudo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.9.5p2-1.el8_10.1 |
| `sudo-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.9.5p2-1.el8_10.1 |
| `sudo-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.9.5p2-1.el8_10.1 |
| `sudo-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.9.5p2-10.el9_6.1 |
| `sudo-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.9.5p2-10.el9_6.1 |
| `sudo-python-plugin` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.9.5p2-10.el9_6.1 |
| `sudo-python-plugin-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:1.9.5p2-10.el9_6.1 |
| `sudo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.9.5p2-10.el9_6.1 |
| `sudo-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.9.5p2-10.el9_6.1 |
| `sudo-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.9.5p2-10.el9_6.1 |
| `sudo-python-plugin-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.9.5p2-10.el9_6.1 |
| `sudo` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:1.8.29-5.el8_2.3 |
| `sudo-debuginfo` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:1.8.29-5.el8_2.3 |
| `sudo-debugsource` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:1.8.29-5.el8_2.3 |
| `sudo` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:1.8.29-7.el8_4.3 |
| `sudo-debuginfo` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:1.8.29-7.el8_4.3 |
| `sudo-debugsource` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:1.8.29-7.el8_4.3 |
| `sudo` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:1.9.5p2-1.el8_6.1 |
| `sudo-debuginfo` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:1.9.5p2-1.el8_6.1 |
| `sudo-debugsource` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:1.9.5p2-1.el8_6.1 |
| `sudo` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:1.9.5p2-1.el8_6.1 |
| `sudo-debuginfo` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:1.9.5p2-1.el8_6.1 |
| `sudo-debugsource` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:1.9.5p2-1.el8_6.1 |
| `sudo` | Red Hat:rhel_e4s:8.8::baseos | All versions | 0:1.9.5p2-1.el8_8.1 |
| `sudo-debuginfo` | Red Hat:rhel_e4s:8.8::baseos | All versions | 0:1.9.5p2-1.el8_8.1 |
| `sudo-debugsource` | Red Hat:rhel_e4s:8.8::baseos | All versions | 0:1.9.5p2-1.el8_8.1 |
| `sudo-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:1.9.5p2-7.el9_0.5 |
| `sudo-debugsource` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:1.9.5p2-7.el9_0.5 |
| `sudo-python-plugin` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:1.9.5p2-7.el9_0.5 |
| `sudo-python-plugin-debuginfo` | Red Hat:rhel_e4s:9.0::appstream | All versions | 0:1.9.5p2-7.el9_0.5 |
| `sudo` | Red Hat:rhel_e4s:9.0::baseos | All versions | 0:1.9.5p2-7.el9_0.5 |
| `sudo-debuginfo` | Red Hat:rhel_e4s:9.0::baseos | All versions | 0:1.9.5p2-7.el9_0.5 |
| `sudo-debugsource` | Red Hat:rhel_e4s:9.0::baseos | All versions | 0:1.9.5p2-7.el9_0.5 |
| `sudo-python-plugin-debuginfo` | Red Hat:rhel_e4s:9.0::baseos | All versions | 0:1.9.5p2-7.el9_0.5 |
| `sudo-debuginfo` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:1.9.5p2-9.el9_2.3 |
| `sudo-debugsource` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:1.9.5p2-9.el9_2.3 |
| `sudo-python-plugin` | Red Hat:rhel_e4s:9.2::appstream | All versions | 0:1.9.5p2-9.el9_2.3 |

Products: Sudo Project Sudo.

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

Upgrade to a fixed version.

## Is CVE-2025-32462 being exploited?

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

Public exploit code:

- A easy sudo poc by cryingn. (github_poc): https://github.com/CryingN/CVE-2025-32462
- 🔓 Local privilege escalation PoC for CVE-2025-32462 (sudo -h bypass) – gain root via misconfigured sudoers (github_poc): https://github.com/0p5cur/CVE-2025-32462-POC
- Docker PoC for CVE-2025-32462 & CVE-2025-32463 (sudo), based on Stratascale CRU research. (github_poc): https://github.com/MAAYTHM/CVE-2025-32462_32463-Lab
- cve-2025-32462' demo (github_poc): https://github.com/SpongeBob-369/cve-2025-32462
- https://github.com/yonathanpy/CVE-2025-32462-CVE-2025-32463-PoC-Lab (github_poc): https://github.com/yonathanpy/CVE-2025-32462-CVE-2025-32463-PoC-Lab
- CVE-2025-32462 Exploit (github_poc): https://github.com/cybersentinelx1/CVE-2025-32462-Exploit

## Other vulnerabilities in Sudo

- [CVE-2017-1000368](https://insights.sbomify.com/CVE-2017-1000368/): Command injection in n/a (high 8.2)
- [CVE-2015-5602](https://insights.sbomify.com/CVE-2015-5602/): Privilege escalation in n/a (high 7.2)
- [CVE-2022-43995](https://insights.sbomify.com/CVE-2022-43995/): Memory corruption in n/a (high 7.1)
- [CVE-2023-42465](https://insights.sbomify.com/CVE-2023-42465/): Privilege escalation in n/a (high 7.0)
- [CVE-2019-18684](https://insights.sbomify.com/CVE-2019-18684/): Race condition in n/a (high 7.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32462 is a low-severity missing authorization vulnerability in Sudo, published on 30 Jun 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-32462 in the wild and no public exploit code.

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

## Sources

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

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