CVE-2025-65965

What it is

Grype is a vulnerability scanner for container images and filesystems. A credential disclosure vulnerability was found in Grype, affecting versions 0.68.0 through 0.104.0. If registry credentials are defined and the output of grype is written using the --file or --output json=<file> option, the registry credentials will be included unsanitized in the output file. This issue has been patched in version 0.104.1. Users running affected versions of grype can work around this vulnerability by redirecting stdout to a file instead of using the --file or --output options.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. High risk of data exposure.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2025-11-25 20:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-18 20:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 8.2 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2025-11-25 20:16 UTC

Last modified

2026-10-18 20:10 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-212

Record status

Deferred

Attack profile CVSS 4.0 · 8.2

Attack vector

Local

Complexity

Low

Attack requirements

None

Privileges needed

None

User interaction

None

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-65965.md and follow it. Check whether this project is affected by CVE-2025-65965. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge