CVE-2026-35342: CWE-377: Insecure Temporary File in Uutils coreutils
The mktemp utility in uutils coreutils fails to properly handle an empty TMPDIR environment variable. Unlike GNU mktemp, which falls back to /tmp when TMPDIR is an empty string, the uutils implementation treats the empty string as a valid path. This causes temporary files to be created in the current working directory (CWD) instead of the intended secure temporary directory. If the CWD is more permissive or accessible to other users than /tmp, it may lead to unintended information disclosure or unauthorized access to temporary data.
AI Analysis
Technical Summary
The mktemp utility in uutils coreutils improperly handles an empty TMPDIR environment variable by using the current working directory for temporary file creation instead of a secure fallback directory such as /tmp. This behavior differs from GNU mktemp, which defaults to /tmp when TMPDIR is empty. The vulnerability (CWE-377) can lead to insecure temporary file creation, potentially exposing sensitive data if the current directory has permissive access controls. The CVSS 3.1 base score is 3.3, indicating low severity, with local attack vector, low complexity, and limited confidentiality impact. No official patch or remediation level has been published, and no known exploits are reported in the wild.
Potential Impact
Temporary files may be created in a less secure location (the current working directory) instead of a secure temporary directory, potentially allowing unauthorized users with access to that directory to read sensitive temporary data. The confidentiality impact is low, with no impact on integrity or availability reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should avoid setting TMPDIR to an empty string or ensure that the current working directory has strict access permissions to prevent unauthorized access to temporary files.
CVE-2026-35342: CWE-377: Insecure Temporary File in Uutils coreutils
Description
The mktemp utility in uutils coreutils fails to properly handle an empty TMPDIR environment variable. Unlike GNU mktemp, which falls back to /tmp when TMPDIR is an empty string, the uutils implementation treats the empty string as a valid path. This causes temporary files to be created in the current working directory (CWD) instead of the intended secure temporary directory. If the CWD is more permissive or accessible to other users than /tmp, it may lead to unintended information disclosure or unauthorized access to temporary data.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The mktemp utility in uutils coreutils improperly handles an empty TMPDIR environment variable by using the current working directory for temporary file creation instead of a secure fallback directory such as /tmp. This behavior differs from GNU mktemp, which defaults to /tmp when TMPDIR is empty. The vulnerability (CWE-377) can lead to insecure temporary file creation, potentially exposing sensitive data if the current directory has permissive access controls. The CVSS 3.1 base score is 3.3, indicating low severity, with local attack vector, low complexity, and limited confidentiality impact. No official patch or remediation level has been published, and no known exploits are reported in the wild.
Potential Impact
Temporary files may be created in a less secure location (the current working directory) instead of a secure temporary directory, potentially allowing unauthorized users with access to that directory to read sensitive temporary data. The confidentiality impact is low, with no impact on integrity or availability reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should avoid setting TMPDIR to an empty string or ensure that the current working directory has strict access permissions to prevent unauthorized access to temporary files.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- canonical
- Date Reserved
- 2026-04-02T12:58:56.087Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e8f7ce19fe3cd2cdd00c0c
Added to database: 4/22/2026, 4:31:10 PM
Last enriched: 4/22/2026, 5:03:17 PM
Last updated: 4/23/2026, 12:39:17 AM
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.