Registry credential disclosure via unsanitized JSON output
Published Nov 25, 2025 · Updated Nov 25, 2025
Credential disclosure in Anchore Grype 0.68.0 through 0.104.0 allows local users to read registry secrets from JSON scan files. The report document incorporates registry authentication options, and file-output serialization writes the auth array without clearing or redacting its username, password, and token fields. Exposure requires configured registry authentication plus JSON file output or a template referencing Descriptor.Registry.Auth, making every configured secret readable from the resulting file.
Summary
What happened
Credential disclosure in Anchore Grype 0.68.0 through 0.104.0 allows local users to read registry secrets from JSON scan files. The report document incorporates registry authentication options, and file-output serialization writes the auth array without clearing or redacting its username, password, and token fields. Exposure requires configured registry authentication plus JSON file output or a template referencing Descriptor.Registry.Auth, making every configured secret readable from the resulting file.
The record
- CVE
- CVE-2025-65965
- Published
- Nov 25, 2025
- Updated
- Nov 25, 2025
- Vendor
- Anchore
- Product
- Grype
- Classifications
- CWE-212, T1552.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 25, 2025CVE publishedPublication date reported by the CVE source.
- Nov 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.68.0, < 0.104.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo