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.
Published: 2026-07-20
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability is a path traversal flaw in the 'shame next' command of the Shamefile linter. An attacker can supply a crafted shamefile.yaml that contains path traversal sequences, allowing the tool to read and display the contents of files outside the repository, one line at a time, in the terminal of the user who executes the command. Because the flaw can reveal any file accessible to the user, it causes direct information disclosure.

Affected Systems

All users of the Shamefile project before version 0.1.7 are affected. The project is maintained by BKDDFS and the relevant product is Shamefile. The unpatched code path exists in all releases older than 0.1.7, while versions 0.1.7 and later include the fix. No other versions or products are known to be impacted.

Risk and Exploitability

The CVSS score of 5.5 indicates a medium severity. The EPSS score of less than 1 % suggests a very low likelihood of exploitation, and the vulnerability is not yet listed in the CISA KEV catalog. Exploitation requires an attacker to place a malicious shamefile.yaml into a repository and for a user — typically a developer or a CI runner — to execute 'shame next' against that file. Once the command is run, the tool streams the contents of files outside the repository to the terminal, allowing an attacker to read sensitive data.

Generated by OpenCVE AI on July 30, 2026 at 18:23 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Shamefile to version 0.1.7 or later to apply the path traversal fix.
  • Do not execute 'shame next' with files that come from untrusted sources.
  • In continuous integration pipelines, use 'shame me --dry-run' instead of 'shame next' to validate linter warnings without risking file disclosure.

Generated by OpenCVE AI on July 30, 2026 at 18:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-x6p3-76f2-xxvh Shamefile has an arbitrary file read via shamefile.yaml in shame next
History

Thu, 23 Jul 2026 21:45:00 +0000

Type Values Removed Values Added
First Time appeared Bkddfs
Bkddfs shamefile
Vendors & Products Bkddfs
Bkddfs shamefile

Wed, 22 Jul 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 20 Jul 2026 22:15:00 +0000

Type Values Removed Values Added
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.
Title Shamefile has an arbitrary file read via shamefile.yaml in shame next
Weaknesses CWE-22
References
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N'}


Subscriptions

Bkddfs Shamefile
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-22T14:18:13.390Z

Reserved: 2026-05-18T19:50:18.696Z

Link: CVE-2026-47144

cve-icon Vulnrichment

Updated: 2026-07-22T14:18:09.208Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-30T18:30:05Z

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')