Path Traversal in shamefile (CVE-2026-47144)
Summary
Path traversal in shamefile (CVE-2026-47144). Confidential information can be exposed externally. Exploitable via shamefile.yaml. Mitigation: upgrade to 0.1.7 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47144 has been found in shamefile.
Attackers can target a specific entry point like shamefile.yaml over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade shamefile to 0.1.7 or later.
If unsure, ask your IT team or search "shamefile CVE-2026-47144" on the vendor's site.
CVE-2026-47144 (shamefile) — CWE-22 / CVSS v3 5.5
Attack vector: local / unauthenticated
Attack surface: shamefile.yaml
Patched: 0.1.7 — apply immediately
Workaround: Do not run shame next against untrusted shamefile.yaml.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in shamefile. Attackers reach the vulnerable code path via shamefile.yaml without authentication.
Check the vendor advisory for the affected versions of shamefile. Attack surface: shamefile.yaml.
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.
Update to 0.1.7.
Workaround: Do not run shame next against untrusted shamefile.yaml.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'shamefile' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'shamefile' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
shamefileを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Do not run `shame next` against untrusted `shamefile.yaml`.パッチが適用されるまでの応急処置として、Do not run
shame nextagainst untrustedshamefile.yaml. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade shamefile to 0.1.7ステージング環境で 0.1.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com