GHSA-2cxp-xq3c-mjxx: Duplicate Advisory: uutils coreutils' mktemp utility doesn't properly handle an empty TMPDIR environment variable
The mktemp utility in uutils coreutils versions prior to 0.6.0 does not correctly handle an empty TMPDIR environment variable. Instead of falling back to a secure default directory like /tmp, it treats the empty string as a valid path, causing temporary files to be created in the current working directory. This behavior can lead to unintended information disclosure or unauthorized access if the current directory has more permissive access controls than the intended temporary directory.
AI Analysis
Technical Summary
In uutils coreutils' mktemp utility, an empty TMPDIR environment variable is improperly handled. Unlike GNU mktemp, which defaults to /tmp when TMPDIR is empty, uutils mktemp uses the empty string as a directory path, resulting in temporary files being created in the current working directory. This can expose temporary files to unauthorized users if the current directory is less secure than /tmp. This issue affects versions of uutils coreutils prior to 0.6.0.
Potential Impact
Temporary files intended to be created in a secure temporary directory may instead be created in the current working directory. If this directory is accessible by other users or has weaker permissions, it can lead to unintended information disclosure or unauthorized access to temporary data. The impact is limited to confidentiality and does not affect integrity or availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should verify if a fixed version (0.6.0 or later) is available and upgrade accordingly. Until patched, avoid running mktemp with an empty TMPDIR environment variable or ensure the current working directory is secure and not accessible by unauthorized users.
GHSA-2cxp-xq3c-mjxx: Duplicate Advisory: uutils coreutils' mktemp utility doesn't properly handle an empty TMPDIR environment variable
Description
The mktemp utility in uutils coreutils versions prior to 0.6.0 does not correctly handle an empty TMPDIR environment variable. Instead of falling back to a secure default directory like /tmp, it treats the empty string as a valid path, causing temporary files to be created in the current working directory. This behavior can lead to unintended information disclosure or unauthorized access if the current directory has more permissive access controls than the intended temporary directory.
CVSS v3.1
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In uutils coreutils' mktemp utility, an empty TMPDIR environment variable is improperly handled. Unlike GNU mktemp, which defaults to /tmp when TMPDIR is empty, uutils mktemp uses the empty string as a directory path, resulting in temporary files being created in the current working directory. This can expose temporary files to unauthorized users if the current directory is less secure than /tmp. This issue affects versions of uutils coreutils prior to 0.6.0.
Potential Impact
Temporary files intended to be created in a secure temporary directory may instead be created in the current working directory. If this directory is accessible by other users or has weaker permissions, it can lead to unintended information disclosure or unauthorized access to temporary data. The impact is limited to confidentiality and does not affect integrity or availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Users should verify if a fixed version (0.6.0 or later) is available and upgrade accordingly. Until patched, avoid running mktemp with an empty TMPDIR environment variable or ensure the current working directory is secure and not accessible by unauthorized users.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2cxp-xq3c-mjxx
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["crates.io"]
- Database Specific Severity
- LOW
- Cvss Version
- 3.1
Threat ID: 6a4c341b27e9c797195f855a
Added to database: 07/06/2026, 23:02:51 UTC
Last enriched: 07/06/2026, 23:19:38 UTC
Last updated: 07/06/2026, 23:19:38 UTC
Views: 2
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.