Skip to main content
VulnerabilityPublished Updated

CVE-2025-65965: its JSON output · Grype Has a Credential Disclosure Vulnerability

Affects github.com/anchore/grypeSource GCVE Database

0
Compare
Authoritative record:CVE-2025-65965· High 8.2

Not known to be exploited · CVSS 8.2 High : upgrade to 0.104.1 soon.

Data as of 19 Nov 2026, 02:51 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.2
Patch
Available – fixed in 0.104.1
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade github.com/anchore/grype to 0.104.1.

Affected software

ProductAffectedFixed in
Gogithub.com/anchore/grypeAffected
  • >=0.68.0 <0.104.1
Fixed in
  • 0.104.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in Grype version 0.104.1 that fixes this vulnerability. Users should upgrade to version 0.104.1 or later. As a workaround, users can avoid using the --file or --output json=<file> options and instead redirect stdout to a file (e.g., grype --output json alpine:latest > output.json), which properly sanitizes credentials in the output.

Description

Grype versions 0.68.0 through 0.104.0 have a credential disclosure vulnerability where registry authentication credentials may be included unsanitized in JSON output files when using the --file or --output json=<file> options. This affects users who have registry authentication configured via configuration files or environment variables. The vulnerability is fixed in version 0.104.1. A workaround is to redirect stdout to a file instead of using the vulnerable output options.

References

Community reviews

Loading reviews…