# CVE-2026-25630: survey-pdf Upgraded jsPDF Version Due to Security Vulnerability


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Updated:** 5 Feb 2026
- **Also known as:** GHSA-h3q6-jfrg-3x6q

## What is CVE-2026-25630?

CVE-2026-25630 is a vulnerability in survey-pdf. 

### Official description

Reason: This candidate was issued in error.

## Which versions are affected by CVE-2026-25630?

4 open source packages ship an affected version, including survey-pdf.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `survey-pdf` | npm | All versions | 1.12.59 |
| `survey-pdf` | npm | All versions | 1.12.59 |
| `survey-pdf` | npm | From 2.0.0 | 2.5.5 |
| `survey-pdf` | npm | From 2.0.0 | 2.5.5 |

## How do I fix CVE-2026-25630?

Upgrade survey-pdf to a fixed version for your release line: 1.12.59 or 2.5.5.

## Is CVE-2026-25630 being exploited?

There is no known exploitation of CVE-2026-25630 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25630 and fix it if it is affected.

What it is: CVE-2026-25630 is a vulnerability in survey-pdf. 
Exploitation: There is no known exploitation of CVE-2026-25630 in the wild and no public exploit code.

Affected packages and fixed versions:
- survey-pdf (npm): affected all versions; fixed in 1.12.59
- survey-pdf (npm): affected all versions; fixed in 1.12.59
- survey-pdf (npm): affected from 2.0.0; fixed in 2.5.5
- survey-pdf (npm): affected from 2.0.0; fixed in 2.5.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-25630/ (Markdown: https://insights.sbomify.com/CVE-2026-25630/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25630
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25630
- OSV: https://osv.dev/vulnerability/CVE-2026-25630

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-25630/
Summaries are generated and may contain mistakes; the official description above is the record.