LiveActive security incident?Get immediate response
CVE Record

CVE-2025-32462: Sudo before 1.9.17p1, when used with a sudoers file that specifies a host that is neither the current host...

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.

LowCVSS 2.8Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a narrow sudo authorization flaw. In certain host-specific sudoers configurations, a user who is already listed in policy may be allowed to run commands on machines that policy did not intend. It is low severity because it requires local access, privileges in sudoers, and a specific configuration pattern.

Executive priority

Handle through normal patch management, with earlier attention for centrally managed sudoers environments. This is not an emergency based on the supplied evidence, but it can undermine administrative access boundaries on affected hosts.

Technical view

Sudo before 1.9.17p1 can mishandle sudoers host specifications when the policy names a host other than the current host or ALL. The result is an authorization bypass where listed users may execute commands on unintended machines. The CVE is CWE-863 with CVSS 3.1 score 2.8.

Likely exposure

Exposure is most likely on Unix/Linux systems running sudo before 1.9.17p1 with host-specific sudoers entries. Systems using only current-host or ALL host rules are less likely to match the described condition.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation. Abuse requires local access, a sudoers-listed user, and the vulnerable host-matching configuration. Public advisories are available, but the evidence provided does not establish in-the-wild exploitation.

Researcher notes

The key condition is policy shape, not merely sudo presence. Validate host aliases and distributed sudoers templates carefully. Avoid conflating this low-severity host authorization issue with other sudo vulnerabilities disclosed around the same time.

Mitigation direction

  • Upgrade sudo to 1.9.17p1 or the vendor-patched package.
  • Review sudoers host fields for unintended non-current-host entries.
  • Prioritize systems with shared sudoers policy across many hosts.
  • Check OS vendor advisories for package availability and backport status.

Validation and detection

  • Inventory sudo versions across Linux and Unix systems.
  • Inspect sudoers and included files for host-specific rules.
  • Confirm whether affected entries name hosts other than current host or ALL.
  • Verify vendor package status after remediation.
Prepared
Confidence
high
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-32462 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
2.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
3ADP providers
16Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
2.8CVSS 3.1LowCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N1.11.4mitre

Vulnerability scoring details

Base CVSS 3.1 score

2.8Low
CVSS 3.1 vector shape for CVE-2025-32462Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Sudo projectSudo1.8.8unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.