GitHub Advisoryadvisory · PyPI, npm, crates.io

GHSA-x6p3-76f2-xxvh Shamefile has an arbitrary file read via shamefile.yaml in shame next

MEDIUM Published 2026-05-28 Modified 2026-07-20 Official page ↗
Aliases
CVE-2026-47144
Ecosystem
PyPI, npm, crates.io
Packages
shamefile
Severity
Moderate
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Weaknesses
CWE-22
Reviewed
2026-05-28

Affected packages

• PyPI shamefile: < 0.1.7 → fixed in 0.1.7 • npm shamefile: < 0.1.7 → fixed in 0.1.7 • crates.io shamefile: < 0.1.7 → fixed in 0.1.7

Description

Impact 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. Patches Fixed in 0.1.7. Upgrade to either 0.1.7 or later versions to incorporate the patch. Workarounds Do not run `shame next` against untrusted `shamefile.yaml`. Use `shame me --dry-run` for CI validation. Resources • Patch commit: https://github.com/BKDDFS/shamefile/commit/77b0aeea318503582818c708518c601fedc43557 • Pull request: https://github.com/BKDDFS/shamefile/pull/80 • Release: https://github.com/BKDDFS/shamefile/releases/tag/v0.1.7 • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Related

Alias · CVE (1)

  • CVE-2026-47144 Shamefile is a linter for undocumented linter warnings. vulnerability

Weakness · CWE (1)

  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory weakness

References