CVE-2026-54639

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% 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
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

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

Style Dictionary, a build system for creating cross-platform styles, has a prototype pollution vulnerability starting in version 4.3.0 and prior to version 5.4.4. Impact users have: direct usage of convertTokenData(tokens, { output: 'object' });; indirect usage, via using Expand API; and/or indirect usage via SD's transform lifecycle. Impact is high for this when style-dictionary is used as an integration in a NodeJS server application. Impact is moderate for when style-dictionary is used as an integration in a Web application. Impact is low for most common cases where the user of style-dictionary also maintains the tokens, and access is limited via read/write access to the repository/workflows where it is used. A patch has been published in version 5.4.4. The only known workaround is to sanitize token data first. Whether using DTCG format or old Style Dictionary format, check the token data object recursively for any object keys that include __proto__.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
3.1%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 25, 2026

Advisory Details (4)

Auto-updated Jun 24, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

Style Dictionary - Prototype Pollution in convertTokenData utility function · Advisory · style-dictionary/style-dictionary · GitHub

https://github.com/style-dictionary/style-dictionary/security/advisories/GHSA-vj5c-m527-mpff
github_pr Patch Available

fix: prototype pollution in convertTokenData utility

Patch available: style-dictionary/style-dictionary v5.4.4 (PR #1702 merged 2026-06-08)

https://github.com/style-dictionary/style-dictionary/pull/1702
github_commit Patch Available

commit 23b5e8dda143 (style-dictionary/style-dictionary)

Patch available: style-dictionary/style-dictionary v5.4.4 (contains commit 23b5e8dda143)

https://github.com/style-dictionary/style-dictionary/commit/23b5e8dda143441f0d6b8e2b4222e2da98058bc5
github_commit Patch Available

commit 209085d9782c (style-dictionary/style-dictionary)

Patch available: style-dictionary/style-dictionary v4.3.0 (contains commit 209085d9782c)

https://github.com/style-dictionary/style-dictionary/commit/209085d9782cfc0783c4d983f3f1bb2c515954ec

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54639?
CVE-2026-54639 is a high vulnerability published on June 24, 2026. Style Dictionary, a build system for creating cross-platform styles, has a prototype pollution vulnerability starting in version 4.3.0 and prior to version 5.4.4. Impact users have: direct usage of convertTokenData(tokens, { output: 'object' });; indirect usage, via using Expand API; and/or…
When was CVE-2026-54639 disclosed?
CVE-2026-54639 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54639 actively exploited?
CVE-2026-54639 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54639?
CVE-2026-54639 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-54639?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54639, 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

Explore the affected products and dependency analysis for CVE-2026-54639

Explore →

Is Your Infrastructure Affected by CVE-2026-54639?

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

Start Free Scan →Browse All CVEs