Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-27139: CWE-363: Race Condition Enabling Link Following in Go standard library os

0
Low
VulnerabilityCVE-2026-27139cvecve-2026-27139cwe-363
Published: Fri Mar 06 2026 (03/06/2026, 21:28:14 UTC)
Source: CVE Database V5
Vendor/Project: Go standard library
Product: os

Description

On Unix platforms, when listing the contents of a directory using File.ReadDir or File.Readdir the returned FileInfo could reference a file outside of the Root in which the File was opened. The impact of this escape is limited to reading metadata provided by lstat from arbitrary locations on the filesystem without permitting reading or writing files outside the root.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/14/2026, 20:04:52 UTC

Technical Analysis

CVE-2026-27139 is a race condition vulnerability identified in the Go programming language's standard library, specifically within the os package on Unix platforms. The issue arises when applications use File.ReadDir or File.Readdir functions to list directory contents. Due to a race condition, the FileInfo objects returned can reference files outside the root directory initially opened by the File object. This means that metadata retrieved via lstat calls can leak information about files outside the intended directory boundary. However, the vulnerability does not allow reading or writing the actual contents of files outside the root, limiting the scope to metadata exposure only. The vulnerability is classified under CWE-363 (Race Condition), indicating a timing issue that can be exploited to bypass intended access restrictions. The affected Go versions include all versions up to 1.26.0-0. The CVSS v3.1 score is 2.5, reflecting low severity, with attack vector local, high attack complexity, low privileges required, no user interaction, and limited confidentiality impact. No known exploits have been reported in the wild. The root cause is a race condition in directory listing functions that fail to properly constrain FileInfo references within the root directory, potentially allowing an attacker with local access to gather metadata about files outside the intended scope. This information could be used for further reconnaissance or privilege escalation attempts in complex attack chains.

Potential Impact

The primary impact of CVE-2026-27139 is limited confidentiality exposure of filesystem metadata outside the intended root directory. Although the vulnerability does not allow reading or modifying file contents, metadata such as file names, sizes, permissions, and timestamps can be leaked. This information disclosure could assist attackers in mapping the filesystem structure, identifying sensitive files, or planning further attacks. Since exploitation requires local access with low privileges and has high attack complexity, the risk is mitigated in environments with strict access controls. However, in multi-tenant or shared hosting environments where untrusted users have local access, this vulnerability could facilitate reconnaissance. The vulnerability does not affect integrity or availability, and no remote exploitation is possible. Overall, the impact is low but should not be ignored in sensitive or high-security environments.

Mitigation Recommendations

1. Upgrade Go to a version later than 1.26.0-0 once patches addressing CVE-2026-27139 are released by the Go project. 2. Until patches are available, avoid using File.ReadDir or File.Readdir in security-critical contexts where directory traversal or metadata leakage could be exploited. 3. Implement strict filesystem permissions and access controls to limit local user access to sensitive directories and files. 4. Use containerization or sandboxing to isolate processes and reduce the risk of local privilege escalation or information leakage. 5. Monitor and audit local user activities to detect unusual directory listing or metadata access patterns. 6. Consider application-level validation to ensure that file metadata accessed corresponds strictly to intended directories. 7. Educate developers about the risks of race conditions and encourage secure coding practices when handling filesystem operations.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Go
Date Reserved
2026-02-17T19:57:28.435Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69ab4b1fc48b3f10ffddeb13

Added to database: 3/6/2026, 9:46:07 PM

Last enriched: 3/14/2026, 8:04:52 PM

Last updated: 4/21/2026, 4:31:49 AM

Views: 151

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses