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 products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| BKDDFS | shamefile | < 0.1.7 | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| crates.io | shamefile | < 0.1.7 | 0.1.7 | GHSA-x6p3-76f2-xxvh |
| npm | shamefile | < 0.1.7 | 0.1.7 | GHSA-x6p3-76f2-xxvh |
| PyPI | shamefile | < 0.1.7 | 0.1.7 | PYSEC-2026-3065 |
References
- https://github.com/BKDDFS/shamefile/security/advisories/GHSA-x6p3-76f2-xxvh
- https://github.com/BKDDFS/shamefile/pull/80
- https://github.com/BKDDFS/shamefile/commit/77b0aeea318503582818c708518c601fedc43557
- https://github.com/BKDDFS/shamefile/releases/tag/v0.1.7
- https://github.com/pypa/advisory-database/tree/main/vulns/shamefile/PYSEC-2026-3065.yaml