# CVE-2025-69624: Null dereference in n/a

> A crafted PDF can crash Nitro PDF Pro via a null pointer dereference in the JavaScript app.alert() function, causing denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-rrjx-h7jp-ggmg

## What is CVE-2025-69624?

CVE-2025-69624 is a high-severity vulnerability in n/a, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nitro PDF Pro before 14.43 for Windows contains a NULL pointer dereference vulnerability in the JavaScript implementation of app.alert(). When app.alert() is called with more than one argument and the first argument evaluates to null (for example, app.alert(app.activeDocs, true) when app.activeDocs is null), the engine routes the call through a fallback path intended for non-string arguments. In this path, js_ValueToString() is invoked on the null value and returns an invalid string pointer, which is then passed to JS_GetStringChars() without validation. Dereferencing this pointer leads to an access violation and application crash when opening a crafted PDF. For example, 14.41.1.4 and 14.42.0.34 have been reported as vulnerable.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2025-69624?

It affects 1 product.


Products: Gonitro Nitro Pdf Pro.

## How do I fix CVE-2025-69624?

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

## Is CVE-2025-69624 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-8709](https://insights.sbomify.com/CVE-2016-8709/): Memory corruption in Nitro Pro (high 8.8)
- [CVE-2016-8711](https://insights.sbomify.com/CVE-2016-8711/): Memory corruption in Nitro Pro (high 8.8)
- [CVE-2016-8713](https://insights.sbomify.com/CVE-2016-8713/): Memory corruption in Nitro Pro (high 8.8)
- [CVE-2025-69627](https://insights.sbomify.com/CVE-2025-69627/): Use after free in n/a (high 8.4)
- [CVE-2025-66769](https://insights.sbomify.com/CVE-2025-66769/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-69624 and fix it if it is affected.

What it is: CVE-2025-69624 is a high-severity vulnerability in n/a, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-69624 in the wild and no public exploit code.

Affected product: n/a. 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-2025-69624/ (Markdown: https://insights.sbomify.com/CVE-2025-69624/index.md)
```

## Sources

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

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