Which versions of satori are affected by CVE-2026-94545?

satori (npm) versions >= 0.0.27, < 0.33.5 is affected.

Is there a fix for CVE-2026-94545?

Yes. CVE-2026-94545 is fixed in 0.33.5. Upgrade to this version or later.

Is CVE-2026-94545 exploitable, and should I be worried?

Whether CVE-2026-94545 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-94545 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-94545 in satori

Q: What is CVE-2026-94545?

CVE-2026-94545 is a medium-severity security vulnerability in satori (npm), affecting versions >= 0.0.27, < 0.33.5. It is fixed in 0.33.5.

Q: Is there a fix for CVE-2026-94545?

Yes. CVE-2026-94545 is fixed in 0.33.5. Upgrade to this version or later.

Q: Is CVE-2026-94545 exploitable, and should I be worried?

Whether CVE-2026-94545 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-94545 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-94545?

Upgrade satori to 0.33.5 or later.

CVE-2026-94545

CVE-2026-94545 is a medium-severity security vulnerability in satori (npm), affecting versions >= 0.0.27, < 0.33.5. It is fixed in 0.33.5.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Satori-generated SVG has improper escaping

Workaround

No complete workaround exists besides upgrading. Applications that cannot immediately upgrade should not render attacker-controlled content with Satori.

Impact

Satori does not properly escape certain values before including them in generated SVG output. This can allow crafted values to be interpreted as SVG markup.

The impact depends on how the generated SVG is consumed.

Affected versions

satori (>= 0.0.27, < 0.33.5)

Security releases

satori → 0.33.5 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade satori to 0.33.5 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-94545? CVE-2026-94545 is a medium-severity security vulnerability in satori (npm), affecting versions >= 0.0.27, < 0.33.5. It is fixed in 0.33.5.
Which versions of satori are affected by CVE-2026-94545? satori (npm) versions >= 0.0.27, < 0.33.5 is affected.
Is there a fix for CVE-2026-94545? Yes. CVE-2026-94545 is fixed in 0.33.5. Upgrade to this version or later.
Is CVE-2026-94545 exploitable, and should I be worried? Whether CVE-2026-94545 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-94545 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-94545? Upgrade satori to 0.33.5 or later.