Skip to content
Noroxi
NVD / CVE Program· CNA mitre

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 e

Noroxi assessment

Priority: Monitor (action score 36/100)

  • Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 4.4% (FIRST EPSS); higher than 91.5% of all records.
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: sudo (AlmaLinux:10) 1.9.15-8.p5.el10_0.2; sudo-python-plugin (AlmaLinux:10) 1.9.15-8.p5.el10_0.2; sudo (AlmaLinux:8) 1.9.5p2-1.el8_10.1.
  • Severity is disputed: the assigning authority (CNA) scores it 2.8, NVD 8.8.

Low priority for now. Upgrade to sudo (AlmaLinux:10) 1.9.15-8.p5.el10_0.2; sudo-python-plugin (AlmaLinux:10) 1.9.15-8.p5.el10_0.2; sudo (AlmaLinux:8) 1.9.5p2-1.el8_10.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 8.8 · v3.1—Proof of concept Fix available
Published
Jun 30, 2025
Updated
Jul 14, 2026
EPSS
4.4% · 91th percentile

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 4.4%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.8
CNA · mitre
2.8
6.0 point gap

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-32462

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
sudo projectsudo

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • sudo project sudobefore 1.9.17
  • sudo project sudo1.9.17

Versions reported by the vendor

Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.

  • Sudo project Sudo

    • 1.8.8 and later · before 1.9.17p1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10sudobefore 1.9.15-8.p5.el10_0.21.9.15-8.p5.el10_0.2
AlmaLinux:10sudo-python-pluginbefore 1.9.15-8.p5.el10_0.21.9.15-8.p5.el10_0.2
AlmaLinux:8sudobefore 1.9.5p2-1.el8_10.11.9.5p2-1.el8_10.1
AlmaLinux:9sudobefore 1.9.5p2-10.el9_6.11.9.5p2-10.el9_6.1
AlmaLinux:9sudo-python-pluginbefore 1.9.5p2-10.el9_6.11.9.5p2-10.el9_6.1
Alpine:v3.21sudobefore 1.9.17_p1-r01.9.17_p1-r0
Debian:11sudobefore 1.9.5p2-3+deb11u21.9.5p2-3+deb11u2
Debian:12sudobefore 1.9.13p3-1+deb12u21.9.13p3-1+deb12u2
Debian:13sudobefore 1.9.16p2-31.9.16p2-3
openSUSE:Leap 15.6sudobefore 1.9.15p5-150600.3.9.11.9.15p5-150600.3.9.1
openSUSE:Tumbleweedsudobefore 1.9.17p1-1.11.9.17p1-1.1
Red Hat:enterprise_linux:10.0sudobefore 0:1.9.15-8.p5.el10_0.20:1.9.15-8.p5.el10_0.2
Red Hat:enterprise_linux:10.0sudo-debuginfobefore 0:1.9.15-8.p5.el10_0.20:1.9.15-8.p5.el10_0.2
Red Hat:enterprise_linux:10.0sudo-debugsourcebefore 0:1.9.15-8.p5.el10_0.20:1.9.15-8.p5.el10_0.2
Red Hat:enterprise_linux:10.0sudo-python-pluginbefore 0:1.9.15-8.p5.el10_0.20:1.9.15-8.p5.el10_0.2
Red Hat:enterprise_linux:10.0sudo-python-plugin-debuginfobefore 0:1.9.15-8.p5.el10_0.20:1.9.15-8.p5.el10_0.2
Red Hat:enterprise_linux:8::baseossudobefore 0:1.9.5p2-1.el8_10.10:1.9.5p2-1.el8_10.1
Red Hat:enterprise_linux:8::baseossudo-debuginfobefore 0:1.9.5p2-1.el8_10.10:1.9.5p2-1.el8_10.1
Red Hat:enterprise_linux:8::baseossudo-debugsourcebefore 0:1.9.5p2-1.el8_10.10:1.9.5p2-1.el8_10.1
Red Hat:enterprise_linux:9::appstreamsudo-debuginfobefore 0:1.9.5p2-10.el9_6.10:1.9.5p2-10.el9_6.1
Red Hat:enterprise_linux:9::appstreamsudo-debugsourcebefore 0:1.9.5p2-10.el9_6.10:1.9.5p2-10.el9_6.1
Red Hat:enterprise_linux:9::appstreamsudo-python-pluginbefore 0:1.9.5p2-10.el9_6.10:1.9.5p2-10.el9_6.1
Red Hat:enterprise_linux:9::appstreamsudo-python-plugin-debuginfobefore 0:1.9.5p2-10.el9_6.10:1.9.5p2-10.el9_6.1
Red Hat:enterprise_linux:9::baseossudobefore 0:1.9.5p2-10.el9_6.10:1.9.5p2-10.el9_6.1

+40

Other highest-scoring records for the same primary product.

  • CVE-2021-3156Sudo before 1.9.5p2 contains an off-by-one error that can result in a heap-based buffer overflow, which allows privilege escalation to root KEV
    91Now
  • CVE-2025-32463Sudo before 1.9.17p1 allows local users to obtain root access because /etc/nsswitch.conf from a user-controlled directory is used with the -KEV
    78This week
  • CVE-2019-14287In Sudo before 1.8.28, an attacker with access to a Runas ALL sudoer account can bypass certain policy blacklists and session PAM modules, a
    54Plan

Published before and after this one in the same product

  • ← EarlierCVE-2023-42465Dec 22, 2023 · Sudo before 1.9.15 might allow row hammer attacks (for authentication bypass or privilege escalation) because application logic sometimes is
    28Monitor
  • ← EarlierCVE-2023-7090Dec 23, 2023 · Sudo: improper handling of ipa_hostname leads to privilege mismanagement
    35Monitor
  • Later →CVE-2026-35535Apr 2, 2026 · In Sudo through 1.9.17p2 before 3e474c2, a failure of a setuid, setgid, or setgroups call, during a privilege drop before running the mailer
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:sudo1.9.5p2-1.el8_10.1 · AlmaLinux:8Package registry (OSV)
almalinux:sudo-python-plugin1.9.15-8.p5.el10_0.2 · AlmaLinux:10Package registry (OSV)
alpine:sudo1.9.17_p1-r0 · Alpine:v3.21Package registry (OSV)
debian:sudo1.9.13p3-1+deb12u2 · Debian:12Package registry (OSV)
opensuse:sudo1.9.15p5-150600.3.9.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:sudo0:1.9.5p2-1.el8_10.1 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:sudo-debuginfo0:1.9.5p2-1.el8_10.1 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:sudo-debugsource0:1.9.5p2-1.el8_10.1 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:sudo-devel0:1.8.23-10.el7_9.4 · Red Hat:rhel_els:7Package registry (OSV)
red hat:sudo-python-plugin0:1.9.5p2-10.el9_4.1 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:sudo-python-plugin-debuginfo0:1.9.5p2-10.el9_4.1 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
rocky linux:sudo0:1.9.5p2-1.el8_10.1 · Rocky Linux:8Package registry (OSV)
suse:sudo1.8.27-4.54.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:sudo1.9.15p5-150600.3.9.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Exploit-DB entry ×1
  • Proof-of-concept repository on GitHub ×11

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entrylocal2025-07-08
Proof-of-concept repository on GitHubstars:132025-07-03
Proof-of-concept repository on GitHubstars:12025-07-03
Proof-of-concept repository on GitHubstars:02025-07-03
Proof-of-concept repository on GitHubstars:92025-07-04
Proof-of-concept repository on GitHubstars:32025-07-05
Proof-of-concept repository on GitHubstars:52025-07-07
Proof-of-concept repository on GitHubstars:02025-07-11
Proof-of-concept repository on GitHubstars:12025-07-28
Proof-of-concept repository on GitHubstars:02025-12-25
Proof-of-concept repository on GitHubstars:02026-01-13
Proof-of-concept repository on GitHubstars:22026-03-05

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+2 d
  3. TodayNov 10, 2026+497 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records