# CVE-2019-25550: Encrypt PDF 2.3 Denial of Service via Buffer Overflow

> Local attackers can crash Encrypt PDF by pasting long strings into password fields, causing a buffer overflow during PDF import.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-v333-cpp7-h389

## What is CVE-2019-25550?

CVE-2019-25550 is a medium-severity memory corruption vulnerability in Verypdf Encrypt PDF, published on 21 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Encrypt PDF 2.3 contains a buffer overflow vulnerability that allows local attackers to crash the application by inputting excessively long strings into password fields. Attackers can paste a 1000-byte buffer into the User Password or Master Password field in the Settings dialog to trigger an application crash when importing PDF files.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2019-25550?

It affects 1 product.


Products: Verypdf Encrypt Pdf.

## How do I fix CVE-2019-25550?

No fix has been published for CVE-2019-25550 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-25550 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25550 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25550 and fix it if it is affected.

What it is: CVE-2019-25550 is a medium-severity memory corruption vulnerability in Verypdf Encrypt PDF, published on 21 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25550 exists.

Affected product: Verypdf Encrypt PDF. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2019-25550/ (Markdown: https://insights.sbomify.com/CVE-2019-25550/index.md)
```

## Sources

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

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