How severe is CVE-2026-35371?

CVE-2026-35371 has a CVSS score of 3.3/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-35371?

CVE-2026-35371 affects the following packages: uu_id (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2026-35371?

Update uu_id to 0.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-35371 is resolved across your whole dependency graph.

How do I detect CVE-2026-35371 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uu_id, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-35371 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-35371 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-35371 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-35371?

CVE-2026-35371 has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 3th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-35371?

CVE-2026-35371 is classified as CWE-451 (CWE-451). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-35371 published, and has it been updated?

CVE-2026-35371 was published on July 6, 2026 and was last updated on July 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

LOW severity

CVE-2026-35371 — uu_id

LOW

CVE-2026-35371 is a low-severity (CVSS 3.3) CWE-451 vulnerability in uu_id. A fix is available for uu_id — see the affected versions and patch details below.

id: pretty-print uses effective GID instead of effective UID for name lookup

Published

Jul 6, 2026

Updated

Jul 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-35371.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs3th percentile — riskier than 3% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-35371 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 382,621 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🦀uu_id

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

The id utility in uutils coreutils exhibits incorrect behavior in its "pretty print" output when the real UID and effective UID differ. The implementation incorrectly uses the effective GID instead of the effective UID when performing a name lookup for the effective user. This results in misleading diagnostic output that can cause automated scripts or system administrators to make incorrect decisions regarding file permissions or access control.

Zellic finding 3.73. Reported in the Zellic uutils coreutils Program Security Assessment (for Canonical, Jan 2026), audited commit 3a07ffc5a9bd4c283e75afa548ba1f1957bad242.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`uu_id`	all versions	0.6.0`cargo update -p uu_id --precise 0.6.0`

Affected Products

1 product · 1 configurations

Application

coreutilsuutils

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for uu_id, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update uu_id to 0.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-35371 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-35371 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

3.3/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-451CWE-451

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

coreutils

5.9/10

Maintained10/10

Code-Review10/10

Branch-Protection3/10

Assessed Sep 28, 2026

Timeline

Disclosed

Jul 6, 2026

Identifiers

CVE-2026-35371

References

Advisorynvd.nist.gov Webgithub.com Webgithub.com Packagegithub.com

Related vulnerabilities

Also affects uu_id

This CVE is low severity; 1 of 1 other CVE affecting uu_id is rated as high or higher (top: moderate).

CVE-2026-35370

Same weakness: CWE-451

This CVE is low severity; 7 of 7 other CVEs with CWE-451 are rated as high or higher (top: high).

CVE-2026-48760CVE-2026-45064CVE-2026-26320CVE-2025-13082CVE-2024-6429CVE-2024-55889CVE-2022-23646Browse all CWE-451

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedJul 6, 2026

CVE-2026-35371 — uu_id

Exploitation Status

Proof-of-concept exploit code exists

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2026-35371 in your dependencies?