VulnerabilityPublished 22 Apr 2026Updated 11 Nov 2026

CVE-2026-35366: Rust coreutils · The printenv utility in uutils coreutils fails to display environment variables

Affects rust-coreutilsSource GCVE Database

Compare

Authoritative record:CVE-2026-35366· Medium 4.4

Not known to be exploited · CVSS 4.4 Medium.

Data as of 11 Nov 2026, 12:41 UTC

CVSS 3.1 base score

4.4Medium

How severe the flaw is on the 0–10 CVSS scale.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Ubuntu 25.10rust-coreutils`pkg:deb/ubuntu/rust-coreutils?arch=source&distro=questing`Other threats	Affected 0.0.30-1 – 0.2.2-0ubuntu2.1 16 affected builds	Fixed in–
Ubuntu 24.04 LTSrust-coreutils`pkg:deb/ubuntu/rust-coreutils?arch=source&distro=noble`Other threats	Affected 0.0.20-1 – 0.0.24-2 7 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, administrators should be aware that printenv may not show all environment variables, especially those with invalid UTF-8, and consider alternative inspection methods for environment variables.

Description

The printenv utility in the rust-coreutils package fails to display environment variables that contain invalid UTF-8 byte sequences. This behavior deviates from POSIX standards, which allow arbitrary bytes in environment strings. As a result, malicious environment variables with invalid UTF-8 can be silently skipped, potentially allowing adversaries to hide malicious payloads such as LD_PRELOAD values from administrators and security tools.

Impact

This vulnerability allows attackers to hide malicious environment variables from visibility, which could facilitate environment-based attacks like library injection. The impact is limited to confidentiality and integrity, with no direct availability impact. The CVSS score of 4.4 (medium severity) reflects the local attack vector and low complexity but limited scope and impact.

Summary

CVE-2026-35366 describes a vulnerability in the printenv utility of rust-coreutils where environment variables containing invalid UTF-8 byte sequences are not displayed. Instead of printing the raw bytes as POSIX permits, the utility silently omits these entries. This flaw can be exploited by attackers to conceal malicious environment variables, such as those used for library injection attacks, thereby evading detection by inspection or auditing tools.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 12:41 UTC

Technical details

References

Community reviews

Related threats