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.
CVE-2026-47144
MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(medium)
- EG Risk
- 25(Track)EG Risk 25/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity55% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 4.3%
- KEV
- Not listed
Published
May 28, 2026
Last Modified
July 23, 2026
Advisory Details (5)
Auto-updated Jul 20, 2026Patch available. Sources: github_commit, github_pr, github_release, github.
generic
advisory-database/vulns/shamefile/PYSEC-2026-3065.yaml at main · pypa/advisory-database · GitHub
https://github.com/pypa/advisory-database/tree/main/vulns/shamefile/PYSEC-2026-3065.yamlgithub Patch Available
Arbitrary file read via shamefile.yaml in shame next · Advisory · BKDDFS/shamefile · GitHub
Affected: 0.1.7. Upgrade.
https://github.com/BKDDFS/shamefile/security/advisories/GHSA-x6p3-76f2-xxvhgithub_release Patch Available
v0.1.7
Patch available: BKDDFS/shamefile v0.1.7
https://github.com/BKDDFS/shamefile/releases/tag/v0.1.7github_pr Patch Available
fix(main): render shame next snippet from registry, not disk
Patch available: BKDDFS/shamefile v0.1.7 (PR #80 merged 2026-05-17)
https://github.com/BKDDFS/shamefile/pull/80github_commit Patch Available
commit 77b0aeea3185 (BKDDFS/shamefile)
Patch available: BKDDFS/shamefile v0.1.7 (contains commit 77b0aeea3185)
https://github.com/BKDDFS/shamefile/commit/77b0aeea318503582818c708518c601fedc43557Vendor Advisories for CVE-2026-47144(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:17 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-05-28 20:06 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-47144?
CVE-2026-47144 is a medium vulnerability published on May 28, 2026. 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…
When was CVE-2026-47144 disclosed?
CVE-2026-47144 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47144 actively exploited?
CVE-2026-47144 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47144?
CVE-2026-47144 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-47144?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47144, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47144
Is Your Infrastructure Affected by CVE-2026-47144?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.