What is CVE-2026-25630?

CVE-2026-25630 is a critical-severity security vulnerability in survey-pdf (npm), affecting versions <= 1.12.58. It is fixed in 1.12.59, 2.5.5.

Which versions of survey-pdf are affected by CVE-2026-25630?

survey-pdf (npm) versions <= 1.12.58 is affected.

Is there a fix for CVE-2026-25630?

Yes. CVE-2026-25630 is fixed in 1.12.59, 2.5.5. Upgrade to this version or later.

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

Whether CVE-2026-25630 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-25630 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-25630?

Upgrade: survey-pdf to 1.12.59 or later, survey-pdf to 2.5.5 or later.

CVE-2026-25630 in survey-pdf

Q: Which versions of survey-pdf are affected by CVE-2026-25630?

survey-pdf (npm) versions <= 1.12.58 is affected.

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

Yes. CVE-2026-25630 is fixed in 1.12.59, 2.5.5. Upgrade to this version or later.

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

Whether CVE-2026-25630 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-25630 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-25630?

Upgrade: survey-pdf to 1.12.59 or later, survey-pdf to 2.5.5 or later.

Summary

survey-pdf Upgraded jsPDF Version Due to Security Vulnerability

The following security vulnerability was identified in jsPDF versions <=3.0.4: Local File Inclusion/Path Traversal.

Action

Users should upgrade survey-pdf in their projects to v1.12.59+ or v2.5.5+ immediately.

Notes

No other survey-pdf dependencies are affected. This update is fully backward-compatible with previous survey-pdf releases.

Impact

Since SurveyJS PDF Generator depends on jsPDF, any project using survey-pdf v1.12.58 and lower or v2.5.4 and lower could be exposed to this vulnerability.

Affected versions

survey-pdf (<= 1.12.58) survey-pdf (>= 2.0.0, <= 2.5.4)

Security releases

survey-pdf → 1.12.59 (npm) survey-pdf → 2.5.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

SurveyJS PDF Generator has upgraded jsPDF to version >= 4.0.0 and included the fix in the following survey-pdf releases:

Frequently Asked Questions

What is CVE-2026-25630? CVE-2026-25630 is a critical-severity security vulnerability in survey-pdf (npm), affecting versions <= 1.12.58. It is fixed in 1.12.59, 2.5.5.
Which versions of survey-pdf are affected by CVE-2026-25630? survey-pdf (npm) versions <= 1.12.58 is affected.
Is there a fix for CVE-2026-25630? Yes. CVE-2026-25630 is fixed in 1.12.59, 2.5.5. Upgrade to this version or later.
Is CVE-2026-25630 exploitable, and should I be worried? Whether CVE-2026-25630 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-25630 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-25630?
- Upgrade survey-pdf to 1.12.59 or later
- Upgrade survey-pdf to 2.5.5 or later