Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2026-35370: Incorrect group membership output in uutils coreutils id

Published Apr 22, 2026 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS4.4Medium · v3.1
EPSS0.11%1st percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Uutils
IdentifiersCVE-2026-35370CWE-682

The id utility in uutils coreutils incorrectly computes the groups= portion of its output by using the invoking user's real GID rather than the effective GID when determining group membership. This causes output that can diverge from GNU coreutils behavior in contexts where real and effective credentials differ. Because the id command is commonly consumed by shell scripts, wrappers, and automated policy logic, the flaw can propagate incorrect authorization context to downstream decision-making.

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.

An attacker who can cause a privileged or security-sensitive workflow to rely on the incorrect id output may trigger improper access-control or permission decisions. The primary impact is logic-level security failure: scripts or automation may incorrectly conclude that a process belongs to a different set of groups than it effectively does, potentially resulting in unauthorized access, unsafe execution paths, or security misconfiguration.

Mitigation

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

Until patched, avoid using uutils coreutils id in security-critical scripts or automated access-control logic, especially in environments where real and effective GIDs may differ, such as setuid/setgid or privilege-transition contexts. Prefer GNU coreutils id or direct system APIs for credential and group resolution where correctness is security-relevant.

Remediation

Patch, then assume compromise.

Upgrade uutils coreutils to version 0.6.0 or later, which is identified in the provided advisory as containing the fix. Validate any security-sensitive scripts or automation that parse id output to ensure they behave correctly after upgrade and, where possible, avoid relying on text parsing of command output for authorization decisions.

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-35370 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2026-35370 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-35370?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2026-35370.
Is there a patch for CVE-2026-35370?
Upgrade uutils coreutils to version 0.6.0 or later, which is identified in the provided advisory as containing the fix. Validate any security-sensitive scripts or automation that parse id output to ensure they behave correctly after upgrade and, where possible, avoid relying on text parsing of command output for authorization decisions.
What products are affected by CVE-2026-35370?
Uutils Coreutils.
How severe is CVE-2026-35370?
CVE-2026-35370 has a CVSS v3.1 score of 4.4 (Medium) and an EPSS score of 0.11% (1st percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

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 activity1Community discussion across Reddit, Mastodon, and other social sources.