What is CVE-2025-32463?

CVE-2025-32463 is Sudo Inclusion of Functionality from Untrusted Control Sphere Vulnerability. The supplied enrichment data classifies it as Unclassified mapped to CWE-829 CWE-829.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

157 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with Not reported where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2025-32463 using CVSS 7.8, EPSS 59%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: HAZY TIGER (), APT 5 (), APT 22 (), Operation Red Signature (), Red October (). Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVhighpublic exploit

CVE-2025-32463

CVE-2025-32463 — Sudo Inclusion of Functionality from Untrusted Control Sphere Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2025-32463 in CISA KEV with 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.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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.

Published Jun 30, 2025Updated Jun 17, 2026Sources: NVD, Sudo project (CNA), CISA, FIRST EPSS, Exploit-DB, Red Hat (VEX), SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Sep 29, 2025

EPSS

59%

ahead of 99.1% of scored CVEs

Affects

Sudo project

Sudo

CVSS base

7.8

high · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Sudo to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

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.

Federal deadline Oct 20, 2025 — passed 335 days ago

Red Hat VEX · CVE-2025-32463

fixed33affected0not affected12

vendor_fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, appli…

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Sudo project	Sudo	1.9.14 to < 1.9.17p1	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Local

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.3	CVSS 3.1	critical	2.5	6	MITRE (CNA), Sudo project (CNA)
7.8	CVSS 3.1	high	1.8	5.9	NVD, Red Hat (VEX)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-829 · Inclusion of Functionality from Untrusted Control Sphere

Execute Unauthorized Code or Commands

Mitigation: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.

Weakness & attack patterns

CWE-829

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-252 · PHP Local File InclusionCAPEC-228 · DTD InjectionCAPEC-549 · Local Execution of CodeCAPEC-253 · Remote Code InclusionCAPEC-201 · Serialized Data External LinkingCAPEC-175 · Code InclusionCAPEC-263 · Force Use of Corrupted FilesCAPEC-251 · Local Code Inclusion

T1055Process Injection
T1195.001Supply Chain Compromise: Software Dependencies and Development Tools
T1505.005Server Software Component: Terminal Services DLL

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Sep 29, 2025

Federal deadline

Oct 20, 2025

passed 335 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

105

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

35 more posts on this CVEShowing 5 of 40 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /etc/nsswitch.conf.
Monitor for scanner or exploit-pattern traffic after 157 public PoC repositories were reported.

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

HAZY TIGERAPT 5APT 22Operation Red SignatureRed October

3 more threat groups on this CVEShowing 5 of 8 · Attribution, campaigns and the malware each one runsUnlock free

ip216.106.183.3553
AbuseIPDB Hourly Update · Apr 24, 2026
ip103.149.168.1885
dan.me.uk-Firehol · Jun 17, 2025
hash3ab9575225e00a83a4ac2b534da5a710bdcf6eb72884944c437b5fbe5c5c923599
AlienVault OTX Feeds · Oct 19, 2025
hash42bcc743c71a9ea083c1c750a39811058279676299
SOCRadar Threat Exchange Services · Nov 20, 2025
hash4200b46a93c6ab059e2b34ce200c4a5b99
SOCRadar Threat Exchange Services · Nov 20, 2025

5 more indicators on this CVEShowing 5 of 10 · Hashes, addresses and domains from a live threat exchangeUnlock free

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Cve is exploited 0xdak/CVE-2025-32463_exploit
Aug 5, 2026 · SOCRadar CTI
Cve is exploited secvulnhub/CVE-2025-32463-EXPLOIT
Jul 7, 2026 · SOCRadar CTI
Cve is exploited Fomovet/cve-2025-32463
Jun 22, 2026 · SOCRadar CTI
Added · CVSS 3.1 7.8 (AV:L)
Jun 17, 2026 · NVD
Cve is exploited 0xzap/CVE-2025-32463
Mar 26, 2026 · SOCRadar CTI
Cve is exploited 12bijaya/CVE-2025-32463
Mar 7, 2026 · SOCRadar CTI
Cve is exploited yonathanpy/CVE-2025-32462-CVE-2025-32463-PoC-Lab
Mar 5, 2026 · SOCRadar CTI
2025
Added to CISA KEV catalog
Sep 29, 2025 · CISA
Added · local entry: Sudo chroot 1.9.17 - Local Privilege Escalation
Jul 8, 2025 · Exploit-DB
Initial · CVE published
Jun 30, 2025 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

16×SVRS was changedMar 7, 2026 – Aug 5, 2026 · SOCRadar CTI
7×Github ReposMar 3, 2026 – Aug 4, 2026 · SOCRadar CTI
4×Tweets · 1 time tweeted.Apr 14, 2026 – Jul 3, 2026 · SOCRadar CTI

References

23 on the record

access.redhat.com/security/cve/cve-2025-32463
Third Party Advisory, Vendor Advisory, NIST
bugs.gentoo.org/show_bug.cgi?id=CVE-2025-32463
Issue Tracking, Third Party Advisory, NIST
explore.alas.aws.amazon.com/CVE-2025-32463.html
Third Party Advisory, NIST
security-tracker.debian.org/tracker/CVE-2025-32463
Third Party Advisory, NIST
ubuntu.com/security/notices/USN-7604-1
Third Party Advisory, NIST
www.openwall.com/lists/oss-security/2025/06/30/3
Third Party Advisory, NIST
www.secpod.com/blog/sudo-lpe-vulnerabilities-resolved-what-you-need-to-know-about-cve-2025-32462-and-cve-2025-32463/
Exploit, Third Party Advisory, NIST
www.stratascale.com/vulnerability-alert-CVE-2025-32463-sudo-chroot
Exploit, Third Party Advisory, NIST, GITHUB

Coverage

13 stories from the feeds we poll

8 more reports on this CVEShowing 5 of 13 · Vendor research and security press coverageUnlock free

Elsewhere on this site

Sudo projectevery CVE for this vendor
September 2025what else CISA listed
Unclassifiedsame class
CWE-829other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 5 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2025-32463 is Sudo Inclusion of Functionality from Untrusted Control Sphere Vulnerability, a high vulnerability affecting Sudo from Sudo project. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 157 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.8 describes technical severity, while EPSS 59% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.