CVE-2026-35535: In Sudo through 1.9.17p2 before 3e474c2, a failure of a setuid, setgid, or setgroups call, during a privile...
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, is not a fatal error and can lead to privilege escalation.
Security readout for executives and security teams
Plain-English summary
A flaw in Sudo can leave a mail-handling process with more privilege than intended when an operating-system privilege-drop call fails. Successful abuse could give a local attacker extensive control over an affected system. The CVSS score is 7.4, reflecting high impact but high exploitation complexity.
Executive priority
Treat as a high-priority local privilege-escalation issue, especially on shared or security-sensitive systems. Patch through supported vendor channels after confirming affected packages. It is not presented as an internet-remote flaw, exploitation requires high complexity, and the supplied evidence does not show active exploitation; these factors support urgent, risk-based remediation rather than emergency-wide shutdown.
Technical view
In Sudo through 1.9.17p2, before commit 3e474c2, failures from setuid, setgid, or setgroups during the pre-mailer privilege drop are not fatal. The mailer may consequently execute with unintended privileges, enabling escalation. The issue maps to CWE-271 and CWE-272 and has vector CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
Likely exposure
Potential exposure exists on systems running Sudo through 1.9.17p2 without the referenced fix. Exploitation is local and high-complexity. The bundle's affected-version metadata is inconsistent, listing version “0” with default status unaffected, so administrators should confirm distribution-specific package status through vendor advisories.
Exploitation context
The bundle does not identify this CVE as KEV, and no supplied source evidence establishes active exploitation. Public technical research is referenced, but that alone does not prove attacks in the wild. The CVSS vector indicates local access, no prior privileges, no user interaction, and high attack complexity.
Researcher notes
The security boundary failure is improper handling of unsuccessful privilege relinquishment before invoking the mailer. Researchers should review vendor backports because package version strings may not directly match upstream releases. Exact triggering conditions, reachable mailer configurations, and distribution-specific exposure are not fully established by the supplied bundle, and its affected-product metadata is internally inconsistent.
Mitigation direction
Install the distribution-supported Sudo update that incorporates commit 3e474c2 or its backported equivalent.
Consult the relevant Linux or product vendor advisory for exact fixed package versions.
Prioritize shared, multi-user, administrative, and other systems where local untrusted access is possible.
Apply temporary vendor-recommended mitigations if patching cannot occur promptly; none are specified in the bundle.
Validation and detection
Inventory installed Sudo package versions across Linux, Unix-like, appliance, and embedded estates.
Compare each package release against its distribution or product vendor advisory, including backported fixes.
Confirm the deployed source or package contains the behavioral change from commit 3e474c2.
After updating, verify package integrity and record the remediated version in vulnerability-management evidence.
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 · low confidence lookup
CWE-271: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
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.
2CVSS vectors
5Timeline events
4ADP providers
35Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-271 · source CWE mapping
Privilege Dropping / Lowering Errors
Privilege Dropping / Lowering Errors represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Least Privilege Violation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.