Loading story…
The maintainers of Style Dictionary patched a prototype pollution vulnerability in the convertTokenData() utility, tracked as GHSA-vj5c-m527-mpff, after finding that malicious token keys containing __proto__ could modify Object.prototype during conversion back into object form. The flaw affects versions 4.3.0 through 5.4.3 and can be reached through direct calls to convertTokenData(), indirectly via the Expand API, or during the project’s transform lifecycle when token data is synchronized into objects.
The fix was merged in commit 23b5e8d through pull request #1702 after linked security issue #1699 was resolved, and it adds a guard that ignores tokens whose keys include __proto__, along with a test confirming that payloads such as {__proto__.a} no longer pollute global object properties. The advisory says impact is greatest when Style Dictionary is embedded in Node.js server applications, moderate in web applications, and lower where token input is tightly controlled; users should upgrade to version 5.4.4, or recursively sanitize token data for __proto__ keys as a workaround.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
A GitHub security advisory disclosed a prototype pollution vulnerability in style-dictionary affecting versions 4.3.0 through 5.4.3. The advisory said the issue was fixed in version 5.4.4 and recommended sanitizing token data for __proto__ keys as a workaround on vulnerable versions.
A pull request to fix prototype pollution in style-dictionary's convertTokenData() utility was merged into the main branch after passing checks. The patch added a guard to ignore token keys containing __proto__ and included a test to verify Object.prototype is not polluted.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
4 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcegithub.com
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Two critical prototype pollution vulnerabilities, **CVE-2026-48713** and **CVE-2026-48714**, were disclosed in the widely used Node.js internationalization components **`i18next-fs-backend`** and **`i18next-http-middleware`**. The bugs allow attacker-controlled missing translation keys to traverse unsafe path segments such as `__proto__`, `constructor`, and `prototype`, potentially writing arbitrary properties into **`Object.prototype`**. In affected deployments, successful exploitation can trigger application crashes, corrupt translation behavior, poison configuration, and bypass property-based security checks. The primary backend flaw affects **`i18next-fs-backend`** versions before **`2.6.6`**, while the middleware flaw affects **`i18next-http-middleware`** versions before **`3.9.7`** and can help remote input reach the vulnerable backend path by failing to block dotted payloads such as `__proto__.polluted`. Exploitation depends on applications exposing **`missingKeyHandler`** or similar **`saveMissing`** functionality to untrusted users with key splitting enabled. Maintainers patched the issues by blocking unsafe path traversal, and defenders are advised to upgrade immediately, restrict missing-key routes to trusted users, disable missing-key persistence for untrusted input, or set **`keySeparator`** to **`false`** where appropriate.
Jun 29, 2026
A high-severity vulnerability tracked as **`CVE-2026-73654`** affects **Trigger.dev** versions **3.3.8 through 4.5.5**, allowing prototype pollution through the **`PUT /api/v1/runs/:runId/metadata`** endpoint. The flaw lets an attacker with a normal environment API key supply malicious metadata keys such as **`__proto__`**, **`constructor`**, or **`prototype`**, which are passed into `JSONHeroPath().set()` and can modify `Object.prototype` in the shared web application process. The resulting corruption can cascade across tenants, causing Prisma query failures, Prometheus label corruption, broken worker authentication, and process-wide denial of service. The issue is classified as **CWE-1321** and carries a **CVSS v3.1** score vector of **`AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H``**, reflecting low-complexity network exploitation with high availability impact. Trigger.dev fixed the vulnerability in **version 4.5.6** by adding input validation, including `isSafeMetadataKey` checks and filtering of dangerous path segments before metadata reaches the path resolver. For self-hosted deployments that cannot patch immediately, recommended interim defenses include WAF rules that inspect HTTP `PUT` requests to the metadata endpoint and block JSON payloads containing unsafe prototype-related keys.
Aug 13, 2026
The maintainers of the Node.js package **`object-path`** released a series of fixes for prototype pollution flaws affecting applications that use the library in inherited-properties mode through **`includeInheritedProps`** or **`withInheritedProps`**. The vulnerable behavior involved methods such as **`set()`**, **`del()`**, **`empty()`**, **`push()`**, and **`insert()`**, where attacker-controlled paths could target magic properties like **`__proto__`** and **`constructor.prototype`** and potentially modify object prototypes. The package documentation states that the default `object-path` instance in versions `0.11.0` and later was not affected. A follow-up hardening change closed a bypass of the earlier mitigation by blocking dangerous paths supplied as non-string or non-numeric values, including nested array path components. Repository tests show the library now rejects attempts to write through prototype-linked paths and raises errors containing **"For security reasons"** when `objectPath.withInheritedProps.set` is used with those values. Version `0.11.8` also added protections to **`get()`**, causing it to throw when code attempts to access restricted properties such as **`__proto__`** or **`constructor`** in inherited-props mode.
Jun 29, 2026