NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

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

mediumCVSS 3.1 5.5GHSA-x6p3-76f2-xxvh

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.

Published May 28, 2026 · Updated Jul 20, 2026

Affected packages

shamefile

Ecosystem
PyPI
Affected
<= 0.1.6
Fixed in
0.1.7
Check
pip show shamefile

shamefile

Ecosystem
npm
Affected
<= 0.1.6
Fixed in
0.1.7
Check
npm ls shamefile

shamefile

Ecosystem
Rust (crates.io)
Affected
<= 0.1.6
Fixed in
0.1.7
Check
cargo tree -i shamefile

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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

Credited to BKDDFS.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology