CVE-2026-47144

MEDIUMPre-NVD 5.55.5
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 5.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.0%, top 98% 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: cna:github_m, epss
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.

Shamefile has an arbitrary file read via shamefile.yaml in shame next

Impact

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.

Patches

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

Workarounds

Do not run shame next against untrusted shamefile.yaml. Use shame me --dry-run for CI validation.

Resources

CVSS v3
5.5
EG Score
5.5(low)
EPSS
2.3%
KEV
Not listed

Published

May 28, 2026

Last Modified

May 28, 2026

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—

Data Freshness Timeline

(refreshed 2× in last 7d / 13× 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-07-16 02:41 UTCEG score recompute
  2. 2026-07-11 19:19 UTCEG score recompute
  3. 2026-07-08 17:46 UTCEG score recompute
  4. 2026-07-02 10:19 UTCEG score recompute
  5. 2026-07-01 02:30 UTCEG score recompute
  6. 2026-06-29 20:53 UTCEG score recompute
  7. 2026-06-28 19:55 UTCEG score recompute
  8. 2026-06-27 18:51 UTCEG score recompute
  9. 2026-06-26 18:02 UTCEG score recompute
  10. 2026-06-25 17:09 UTCEG score recompute
  11. 2026-06-24 16:20 UTCEG score recompute
  12. 2026-06-18 23:51 UTCEG score recompute
  13. 2026-06-17 17:48 UTCEG score recompute
  14. 2026-06-16 15:36 UTCEG score recompute
  15. 2026-06-15 12:49 UTCEG score recompute
  16. 2026-06-14 23:18 UTCEPSS rescore
  17. 2026-06-14 11:43 UTCEG score recompute
  18. 2026-06-13 23:00 UTCEPSS rescore
  19. 2026-06-13 10:52 UTCEG score recompute
  20. 2026-06-12 23:12 UTCEPSS rescore
  21. 2026-06-12 09:59 UTCEG score recompute
  22. 2026-06-11 09:10 UTCEG score recompute
  23. 2026-06-10 08:22 UTCEG score recompute
  24. 2026-06-09 07:33 UTCEG score recompute
  25. 2026-06-08 06:43 UTCEG score recompute
Show 8 more
  1. 2026-06-07 05:55 UTCEG score recompute
  2. 2026-06-06 05:06 UTCEG score recompute
  3. 2026-06-05 04:17 UTCEG score recompute
  4. 2026-06-04 03:28 UTCEG score recompute
  5. 2026-06-03 02:39 UTCEG score recompute
  6. 2026-06-02 01:50 UTCEG score recompute
  7. 2026-06-01 01:01 UTCEG score recompute
  8. 2026-05-28 20:06 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-47144?
CVE-2026-47144 is a medium vulnerability published on May 28, 2026. Shamefile has an arbitrary file read via shamefile.yaml in shame next Impact 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…
When was CVE-2026-47144 disclosed?
CVE-2026-47144 was first published in the National Vulnerability Database on May 28, 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 2.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 v4.0 base score of 5.5 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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