Vulnerability · Published Jul 20, 2026 · Assigned by GitHub_M

CVE-2026-47144Shamefile has an arbitrary file read via shamefile.yaml in shame next

Medium 5.5

In plain English

A medium-severity path traversal in shamefile from BKDDFS. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 8% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)5.5Medium
Exploit odds (30 days)0.2%top 92.0% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
PyPIshamefile0.1.7GHSA-x6p3-76f2-xxvh
PyPIshamefile0.1.7PYSEC-2026-3065
npmshamefile0.1.7GHSA-x6p3-76f2-xxvh

Affected products (as reported)

VendorProductVersions
BKDDFS shamefile < 0.1.7

Weakness: CWE-22 · Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

References