CVE-2025-32462

CVE-2025-32462 is a low-severity vulnerability in Sudo Project Sudo with a CVSS 3.x base score of 2.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-863.

Key facts

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.

Frequently asked questions

What is CVE-2025-32462?
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.
How severe is CVE-2025-32462?
CVE-2025-32462 has a CVSS 3.x base score of 2.8, rated low severity. It is exploitable over local access with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2025-32462 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (87th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-32462?
CVE-2025-32462 primarily affects Sudo Project Sudo. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-32462?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-32462 have an EU (EUVD) identifier?
Yes. CVE-2025-32462 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-20867.
When was CVE-2025-32462 published?
CVE-2025-32462 was published on 2025-06-30 and last updated on 2026-06-17.

References

Affected products (2)

More vulnerabilities in Sudo Project Sudo

All CVEs affecting Sudo Project Sudo →

Other CWE-863 (Incorrect Authorization) vulnerabilities

Browse all CWE-863 (Incorrect Authorization) vulnerabilities →