https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 12:05:12 +0000 https://vulnerability.circl.lu/vuln/brew-style-dictionary-cve-2026-54639 <p><strong>Affected:</strong> Homebrew: style-dictionary</p> <p>### Impact Prototype pollution. A malicious user can create a token array `[{ key: &#39;{__proto__.foo}&#39;, value: &#39;malicious&#39; }]`, when processed by `convertTokenData()` utility function, it will pollute the Object.prototype globally where `{}.foo` will equal `{ key: &#39;{__proto__.foo}&#39;, value: &#39;malicious&#39; }`.</p> <p>This has been confirmed with a test/reproduction.</p> <p>You are impacted when: - direct usage of `convertTokenData(tokens, { output: &#39;object&#39; });` - indirect usage, via using Expand API https://styledictionary.com/reference/config/#expand. If your expand config deems it necessary to run expand (this means, if NOT: 1) set to false, 2) all subprops set to false, or 3) undefined), then we sync the `sd.tokens` property with the `sd.tokenMap` property by converting tokenData map back to object. - indirect usage via SD&#39;s transform lifecycle. Once your tokens are transformed, we also have to sync the `sd.tokens` property with the `sd.tokenMap` property.</p> <p>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.</p> <p>### Patches A patch has been published: version `5.4.4`. Any version within range `&gt;=4.3.0 &lt;5.4.4` contains this vulnerability, see commit hash 209085d for…</p> <p><strong>Affected:</strong> Homebrew: style-dictionary</p> <p>### Impact Prototype pollution. A malicious user can create a token array `[{ key: &#39;{__proto__.foo}&#39;, value: &#39;malicious&#39; }]`, when processed by `convertTokenData()` utility function, it will pollute the Object.prototype globally where `{}.foo` will equal `{ key: &#39;{__proto__.foo}&#39;, value: &#39;malicious&#39; }`.</p> <p>This has been confirmed with a test/reproduction.</p> <p>You are impacted when: - direct usage of `convertTokenData(tokens, { output: &#39;object&#39; });` - indirect usage, via using Expand API https://styledictionary.com/reference/config/#expand. If your expand config deems it necessary to run expand (this means, if NOT: 1) set to false, 2) all subprops set to false, or 3) undefined), then we sync the `sd.tokens` property with the `sd.tokenMap` property by converting tokenData map back to object. - indirect usage via SD&#39;s transform lifecycle. Once your tokens are transformed, we also have to sync the `sd.tokens` property with the `sd.tokenMap` property.</p> <p>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.</p> <p>### Patches A patch has been published: version `5.4.4`. Any version within range `&gt;=4.3.0 &lt;5.4.4` contains this vulnerability, see commit hash 209085d for…</p> https://vulnerability.circl.lu/vuln/brew-style-dictionary-cve-2026-54639 https://vulnerability.circl.lu/vuln/fkie_cve-2026-54639 <p>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: &#39;object&#39; });`; indirect usage, via using Expand API; and/or indirect usage via SD&#39;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__`.</p> <p>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: &#39;object&#39; });`; indirect usage, via using Expand API; and/or indirect usage via SD&#39;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__`.</p> https://vulnerability.circl.lu/vuln/fkie_cve-2026-54639 https://vulnerability.circl.lu/vuln/ghsa-vj5c-m527-mpff <p><strong>Affected:</strong> npm: style-dictionary</p> <p>### Impact Prototype pollution. A malicious user can create a token array `[{ key: &#39;{__proto__.foo}&#39;, value: &#39;malicious&#39; }]`, when processed by `convertTokenData()` utility function, it will pollute the Object.prototype globally where `{}.foo` will equal `{ key: &#39;{__proto__.foo}&#39;, value: &#39;malicious&#39; }`.</p> <p>This has been confirmed with a test/reproduction.</p> <p>You are impacted when: - direct usage of `convertTokenData(tokens, { output: &#39;object&#39; });` - indirect usage, via using Expand API https://styledictionary.com/reference/config/#expand. If your expand config deems it necessary to run expand (this means, if NOT: 1) set to false, 2) all subprops set to false, or 3) undefined), then we sync the `sd.tokens` property with the `sd.tokenMap` property by converting tokenData map back to object. - indirect usage via SD&#39;s transform lifecycle. Once your tokens are transformed, we also have to sync the `sd.tokens` property with the `sd.tokenMap` property.</p> <p>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.</p> <p>### Patches A patch has been published: version `5.4.4`. Any version within range `&gt;=4.3.0 &lt;5.4.4` contains this vulnerability, see commit hash 209085d for…</p> <p><strong>Affected:</strong> npm: style-dictionary</p> <p>### Impact Prototype pollution. A malicious user can create a token array `[{ key: &#39;{__proto__.foo}&#39;, value: &#39;malicious&#39; }]`, when processed by `convertTokenData()` utility function, it will pollute the Object.prototype globally where `{}.foo` will equal `{ key: &#39;{__proto__.foo}&#39;, value: &#39;malicious&#39; }`.</p> <p>This has been confirmed with a test/reproduction.</p> <p>You are impacted when: - direct usage of `convertTokenData(tokens, { output: &#39;object&#39; });` - indirect usage, via using Expand API https://styledictionary.com/reference/config/#expand. If your expand config deems it necessary to run expand (this means, if NOT: 1) set to false, 2) all subprops set to false, or 3) undefined), then we sync the `sd.tokens` property with the `sd.tokenMap` property by converting tokenData map back to object. - indirect usage via SD&#39;s transform lifecycle. Once your tokens are transformed, we also have to sync the `sd.tokens` property with the `sd.tokenMap` property.</p> <p>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.</p> <p>### Patches A patch has been published: version `5.4.4`. Any version within range `&gt;=4.3.0 &lt;5.4.4` contains this vulnerability, see commit hash 209085d for…</p> https://vulnerability.circl.lu/vuln/ghsa-vj5c-m527-mpff