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.
Why It Matters
Analysis dossierWhy It Matters
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.
Immediate Attention
Yes
Unknown
Risk basis: CISA KEV exploitation signal; SOC ecosystem technology relevance; CRITICAL severity; Known exploitation signal from CISA KEV or ransomware metadata; Source-confirmed exploitation or CISA KEV/ransomware metadata
Affected Products & Remediation
8 source-backed products- sudo project sudo · >= 1.9.14 < 1.9.17; 1.9.17 · NVD CPE · Source
- canonical ubuntu linux · 22.04; 24.04; 24.10; 25.04 · NVD CPE · Source
- debian debian linux · 11.0; 12.0; 13.0 · NVD CPE · Source
- opensuse leap · 15.6 · NVD CPE · Source
- redhat enterprise linux · 10.0 · NVD CPE · Source
- suse linux enterprise desktop · 15 · NVD CPE · Source
- suse linux enterprise real time · 15.0 · NVD CPE · Source
- suse linux enterprise server for sap · 12 · NVD CPE · Source
Vendor or catalog guidance (source)
- CISA KEV: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Known exploitation (source facts)
Only what a source states. Unknown means no source has said either way; it is not "not exploited".
- CISA KEV
- Listed
- Exploited (source statement)
- Yes
- Publicly disclosed (source)
- Unknown
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Suggested hunting (rule-based inference)
SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.
No rule-based guidance for this vulnerability class
CISA KEV Record
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Change History & Source Data
— No recorded material change
- CNA / source
- cve@mitre.org
- Record status · verification
- UPDATED · CISA KEV confirmed
- CPE
- cpe:2.3:a:sudo_project:sudo:*:*:*:*:*:*:*:*, cpe:2.3:a:sudo_project:sudo:1.9.17:-:*:*:*:*:*:*, cpe:2.3:o:canonical:ubuntu_linux:22.04:*:*:*:lts:*:*:*, cpe:2.3:o:canonical:ubuntu_linux:24.04:*:*:*:lts:*:*:*, cpe:2.3:o:canonical:ubuntu_linux:24.10:*:*:*:-:*:*:*, cpe:2.3:o:canonical:ubuntu_linux:25.04:*:*:*:-:*:*:*, cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*, cpe:2.3:o:debian:debian_linux:12.0:*:*:*:*:*:*:*, cpe:2.3:o:debian:debian_linux:13.0:*:*:*:*:*:*:*, cpe:2.3:o:opensuse:leap:15.6:*:*:*:*:*:*:*
Evidence & Provenance
Linked by the query's stored exact CVE association. Review required tables and validation status before use.
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2025-32463"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel descLooking up related community queries…