CVE-2026-47144

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')

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.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-47144 has a CVSS score of 5.5 (Medium). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.1.7); upgrading removes the vulnerable code path.

Kodem intelligence

Fixed in 0.1.7. Upgrade to either 0.1.7 or later versions to incorporate the patch.

1. What is CVE-2026-47144? CVE-2026-47144 is a medium-severity path traversal vulnerability in shamefile (pip), affecting versions <= 0.1.6. It is fixed in 0.1.7. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-47144? CVE-2026-47144 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of shamefile are affected by CVE-2026-47144? shamefile (pip) versions <= 0.1.6 is affected.
4. Is there a fix for CVE-2026-47144? Yes. CVE-2026-47144 is fixed in 0.1.7. Upgrade to this version or later.
5. Is CVE-2026-47144 exploitable, and should I be worried? Whether CVE-2026-47144 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-47144 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-47144?
   • Upgrade shamefile to 0.1.7 or later
   • Upgrade shamefile to 0.1.7 or later
   • Upgrade shamefile to 0.1.7 or later