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.2%, top 92% 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.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

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 computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

May 28, 2026

Last Modified

July 23, 2026

Advisory Details (5)

Auto-updated Jul 20, 2026
Patch 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.yaml
github 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-xxvh
github_release Patch Available

v0.1.7

Patch available: BKDDFS/shamefile v0.1.7

https://github.com/BKDDFS/shamefile/releases/tag/v0.1.7
github_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/80
github_commit Patch Available

commit 77b0aeea3185 (BKDDFS/shamefile)

Patch available: BKDDFS/shamefile v0.1.7 (contains commit 77b0aeea3185)

https://github.com/BKDDFS/shamefile/commit/77b0aeea318503582818c708518c601fedc43557

Vendor 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.

Affected Packages

(3 across 3 ecosystems)
crates.io(1)
PackageVulnerable rangeFixed inDependents
shamefile—0.1.7—
npm(1)
PackageVulnerable rangeFixed inDependents
shamefile—0.1.7—
PyPI(1)
PackageVulnerable rangeFixed inDependents
shamefile0.1.0 ... 0.1.6 (9 versions)0.1.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 38× 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.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 04:37 UTCEG score recompute
  11. 2026-08-23 14:26 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 15:23 UTCEG score recompute
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-20 10:42 UTCEG score recompute
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 07:16 UTCEG score recompute
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 02:32 UTCEG score recompute
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 11:11 UTCEG score recompute
Show 44 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-13 10:22 UTCEG score recompute
  3. 2026-08-12 13:51 UTCEPSS rescore
  4. 2026-08-12 09:29 UTCEG score recompute
  5. 2026-08-11 04:29 UTCEG score recompute
  6. 2026-08-11 00:00 UTCEPSS rescore
  7. 2026-08-10 03:40 UTCEG score recompute
  8. 2026-08-09 13:46 UTCEPSS rescore
  9. 2026-08-09 02:52 UTCEG score recompute
  10. 2026-08-08 16:37 UTCEPSS rescore
  11. 2026-08-08 02:03 UTCEG score recompute
  12. 2026-08-07 01:14 UTCEG score recompute
  13. 2026-08-06 13:47 UTCEPSS rescore
  14. 2026-08-06 00:25 UTCEG score recompute
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-04 23:37 UTCEG score recompute
  17. 2026-08-04 15:10 UTCEPSS rescore
  18. 2026-08-04 10:39 UTCEPSS rescore
  19. 2026-08-03 16:05 UTCEG score recompute
  20. 2026-08-03 10:36 UTCEPSS rescore
  21. 2026-08-02 15:12 UTCEG score recompute
  22. 2026-08-02 02:27 UTCEPSS rescore
  23. 2026-08-01 14:23 UTCEG score recompute
  24. 2026-08-01 04:16 UTCEPSS rescore
  25. 2026-07-31 06:17 UTCEG score recompute
  26. 2026-07-30 16:28 UTCEPSS rescore
  27. 2026-07-30 01:30 UTCEPSS rescore
  28. 2026-07-29 12:26 UTCEG score recompute
  29. 2026-07-28 15:37 UTCEPSS rescore
  30. 2026-07-27 14:13 UTCEPSS rescore
  31. 2026-07-27 09:34 UTCEG score recompute
  32. 2026-07-26 14:54 UTCEPSS rescore
  33. 2026-07-26 14:54 UTCEPSS rescore
  34. 2026-07-26 07:38 UTCEG score recompute
  35. 2026-07-25 14:18 UTCEPSS rescore
  36. 2026-07-24 14:17 UTCEPSS rescore
  37. 2026-07-23 14:18 UTCEPSS rescore
  38. 2026-07-23 03:17 UTCEG score recompute
  39. 2026-07-22 14:08 UTCEPSS rescore
  40. 2026-07-21 15:24 UTCEPSS rescore
  41. 2026-06-14 23:18 UTCEPSS rescore
  42. 2026-06-13 23:00 UTCEPSS rescore
  43. 2026-06-12 23:12 UTCEPSS rescore
  44. 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 0% probability of exploitation in the next 30 days, which ranks it in the top 92.0% of all scored CVEs.
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

Explore →

Is Your Infrastructure Affected by CVE-2026-47144?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs