# CVE-2025-67825: Information disclosure in n/a

> Nitro PDF Pro displays unverified signer information instead of verified certificate details, potentially misleading users about document authenticity.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Jan 2026
- **Updated:** 2 Feb 2026
- **Also known as:** GHSA-r4j5-j8m6-jr6p

## What is CVE-2025-67825?

CVE-2025-67825 is a medium-severity vulnerability in n/a, published on 8 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in Nitro PDF Pro for Windows before 14.42.0.34. In certain cases, it displays signer information from a non-verified PDF field rather than from the verified certificate subject. This could allow a document to present inconsistent signer details. The display logic was updated to ensure signer information consistently reflects the verified certificate identity.

Weakness: CWE-346 (Origin Validation Error)

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

It affects 1 product.


Products: Gonitro Nitro Pdf Pro.

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

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

## Is CVE-2025-67825 being exploited?

There is no known exploitation of CVE-2025-67825 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-67825 and fix it if it is affected.

What it is: CVE-2025-67825 is a medium-severity vulnerability in n/a, published on 8 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-67825 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-67825/ (Markdown: https://insights.sbomify.com/CVE-2025-67825/index.md)
```

## Sources

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

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