Advisory

GHSA-x6p3-76f2-xxvh

Also known as: CVE-2026-47144, PYSEC-2026-3065

Summary

Shamefile has an arbitrary file read via shamefile.yaml in shame next

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-05-28 20:02 UTC
Modified
2026-07-20 22:00 UTC

Affected packages and fixes

shamefile

PyPI · All systems

Affected

  • introduced 0, fixed 0.1.7 (ecosystem)

Fixed versions

0.1.7

Fix

  • Fixed version 0.1.7
    pip install --upgrade shamefile==0.1.7

shamefile

npm · All systems

Affected

  • introduced 0, fixed 0.1.7 (semver)

Fixed versions

0.1.7

Fix

shamefile

crates.io · All systems

Affected

  • introduced 0, fixed 0.1.7 (semver)

Fixed versions

0.1.7

Fix

  • Fixed version 0.1.7
    cargo update -p shamefile --precise 0.1.7

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences