Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-35368: Root Code Execution in uutils chroot --userspec via Untrusted NSS Modules

Published Apr 22, 2026 · Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS7.8High · v3.1
EPSS0.14%3rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Uutils
IdentifiersCVE-2026-35368CWE-829

The chroot utility in uutils coreutils resolves the user specified by --userspec using getpwnam() after entering the new root directory but before dropping root privileges. On glibc-based systems, this lookup can cause Name Service Switch (NSS) shared libraries to be loaded from the new root. An attacker who controls the relevant contents of that directory can supply a malicious NSS module that executes with root privileges. The vulnerability can enable local privilege escalation or escape from chroot-based isolation.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits arbitrary code execution as root in the privileged chroot process, potentially compromising system confidentiality, integrity, and availability. It can enable privilege escalation and, where the process retains sufficient privileges and is not constrained by additional isolation controls, escape from chroot or container isolation.

Mitigation

If you can’t patch tonight, do this now.

Avoid privileged use of the affected chroot utility with --userspec when the new root directory is attacker-controlled or attacker-writable. Restrict modification of the new root's NSS configuration, library locations, and their parent directories to trusted administrators. Do not rely on chroot alone to contain untrusted code.

Remediation

Patch, then assume compromise.

Install vendor security updates addressing CVE-2026-35368. For Ubuntu 26.04 LTS systems using rust-coreutils, apply the package update associated with USN-9041-1. An exact fixed package version is not available in the supplied information.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
UutilsCoreutilsapplication
FAQ

Frequently asked questions

Is CVE-2026-35368 exploited in the wild?
As of Nov 14, 2026, Mallory has no reports of CVE-2026-35368 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-35368?
Yes. As of Nov 14, 2026, Mallory has reports of a public exploit for CVE-2026-35368.
Is there a patch for CVE-2026-35368?
Install vendor security updates addressing CVE-2026-35368. For Ubuntu 26.04 LTS systems using rust-coreutils, apply the package update associated with USN-9041-1.
What products are affected by CVE-2026-35368?
Uutils Coreutils.
How severe is CVE-2026-35368?
CVE-2026-35368 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.14% (3rd percentile) as of Nov 14, 2026.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.