CVE-2026-47144

Received Received - Intake

Path Traversal in Shamefile via shame next

Publication date: 2026-07-20

Last updated on: 2026-07-20

Assigner: GitHub, Inc.

Description

Shamefile is a linter for undocumented linter warnings. Prior to version 0.1.7, a path traversal vulnerability in `shame next` allows an attacker-controlled `shamefile.yaml` to disclose contents of files outside the repository, one line at a time, to the terminal of a user who runs the command. See patch commit for technical details. The issue is fixed in 0.1.7. Upgrade to either 0.1.7 or later versions to incorporate the patch. As a workaround, do not run `shame next` against untrusted `shamefile.yaml`. Use `shame me --dry-run` for CI validation.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-20

Last Modified

2026-07-20

Generated

2026-07-21

AI Q&A

2026-07-21

EPSS Evaluated

N/A

NVD

CVE-2026-47144

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-22	The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

Executive Summary

Shamefile is a tool that checks for undocumented warnings. A path traversal vulnerability exists in versions before 0.1.7. When running the command `shame next`, an attacker can craft a malicious `shamefile.yaml` file to read files outside the repository one line at a time and display them in the terminal of a user executing the command.

Detection Guidance

To detect this vulnerability, check the version of Shamefile installed on your system. Run: shame --version. If the version is below 0.1.7, the system is vulnerable. Additionally, monitor for suspicious activity when running shame next, such as unexpected file content output.

Impact Analysis

This vulnerability allows an attacker to access sensitive files on your system if you run `shame next` against an untrusted `shamefile.yaml`. The attacker can read files line by line, potentially exposing confidential data such as configuration files or source code.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating compliance requirements under GDPR (data protection) and HIPAA (health information privacy). Unauthorized file access may result in data breaches, triggering legal penalties and reputational damage.

Mitigation Strategies

Upgrade Shamefile to version 0.1.7 or later immediately. If upgrading is not possible, avoid running shame next against untrusted shamefile.yaml files. Use shame me --dry-run for CI validation instead.

Hi! I’m here to help you understand CVE-2026-47144. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70