Is CVE-2026-54639 actively exploited?

No active exploitation of CVE-2026-54639 has been confirmed so far. Continue monitoring, as exploit status can change.

Can CVE-2026-54639 be exploited remotely?

No. CVE-2026-54639 requires local access to exploit.

What is the CVSS score of CVE-2026-54639?

CVE-2026-54639 has a CVSS score of 8.8 (HIGH).

HOME VULNERABILITIESCVE-2026-54639

HIGH

CVE-2026-54639

CWE-1321Published: June 24, 2026· Updated: Jun 25, 2026

8.8

CVSS v3.1

EPSS:0.13%probability of exploitation in 30 daysPercentile:3.0th

Official Description

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__`.

NVD Source

Technical Analysis

CVE-2026-54639 requires local access, meaning attackers must already have a foothold on the target system.

Exploitation requires low privileges, which limits the exposure to scenarios where an attacker has already gained initial access.

A successful exploit results in complete confidentiality breach (data exposure), full integrity compromise (data manipulation), availability disruption (denial of service), with a CVSS base score of 8.8.

The vulnerability has a "Changed" scope, meaning successful exploitation can impact components beyond the vulnerable component itself — such as the host operating system or adjacent services.