CVE-2026-47144: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in BKDDFS shamefile
A path traversal vulnerability exists in BKDDFS shamefile versions prior to 0.1.7. This flaw allows an attacker-controlled shamefile.yaml to disclose contents of files outside the repository one line at a time when running the 'shame next' command. The vulnerability is fixed in version 0.1.7. Users are advised to upgrade to 0.1.7 or later or avoid running 'shame next' against untrusted shamefile.yaml files. Using 'shame me --dry-run' is recommended for CI validation as a safer alternative.
AI Analysis
Technical Summary
CVE-2026-47144 is a path traversal vulnerability (CWE-22) in BKDDFS shamefile, a linter tool. In versions before 0.1.7, the 'shame next' command improperly limits pathname access, allowing an attacker to craft a malicious shamefile.yaml that can read files outside the intended repository scope. This results in disclosure of file contents line by line to the terminal of the user executing the command. The issue is resolved in version 0.1.7 by applying a patch that restricts pathname traversal. The vendor recommends upgrading to 0.1.7 or newer and avoiding running 'shame next' on untrusted input.
Potential Impact
An attacker who can supply a malicious shamefile.yaml can cause the 'shame next' command to disclose sensitive file contents outside the repository boundary to the user's terminal. This leads to confidentiality loss of arbitrary files accessible to the user running the command. There is no impact on integrity or availability. The vulnerability requires local execution with user interaction (UI:R) and low complexity (AC:L).
Mitigation Recommendations
Upgrade BKDDFS shamefile to version 0.1.7 or later, where the vulnerability is fixed. As a workaround, do not run 'shame next' against untrusted shamefile.yaml files. For continuous integration validation, use 'shame me --dry-run' which does not expose this vulnerability. Patch status is confirmed fixed in 0.1.7.
CVE-2026-47144: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in BKDDFS shamefile
Description
A path traversal vulnerability exists in BKDDFS shamefile versions prior to 0.1.7. This flaw allows an attacker-controlled shamefile.yaml to disclose contents of files outside the repository one line at a time when running the 'shame next' command. The vulnerability is fixed in version 0.1.7. Users are advised to upgrade to 0.1.7 or later or avoid running 'shame next' against untrusted shamefile.yaml files. Using 'shame me --dry-run' is recommended for CI validation as a safer alternative.
CVSS v3.1
Score 5.5medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-47144 is a path traversal vulnerability (CWE-22) in BKDDFS shamefile, a linter tool. In versions before 0.1.7, the 'shame next' command improperly limits pathname access, allowing an attacker to craft a malicious shamefile.yaml that can read files outside the intended repository scope. This results in disclosure of file contents line by line to the terminal of the user executing the command. The issue is resolved in version 0.1.7 by applying a patch that restricts pathname traversal. The vendor recommends upgrading to 0.1.7 or newer and avoiding running 'shame next' on untrusted input.
Potential Impact
An attacker who can supply a malicious shamefile.yaml can cause the 'shame next' command to disclose sensitive file contents outside the repository boundary to the user's terminal. This leads to confidentiality loss of arbitrary files accessible to the user running the command. There is no impact on integrity or availability. The vulnerability requires local execution with user interaction (UI:R) and low complexity (AC:L).
Mitigation Recommendations
Upgrade BKDDFS shamefile to version 0.1.7 or later, where the vulnerability is fixed. As a workaround, do not run 'shame next' against untrusted shamefile.yaml files. For continuous integration validation, use 'shame me --dry-run' which does not expose this vulnerability. Patch status is confirmed fixed in 0.1.7.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-18T19:50:18.696Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5e9d432a4a8d5989d506e6
Added to database: 07/20/2026, 22:12:19 UTC
Last enriched: 07/20/2026, 22:27:12 UTC
Last updated: 07/21/2026, 05:06:20 UTC
Views: 14
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.