CVE-2025-65965VulnerabilityPublished 25 Nov 2025

CVE-2025-65965: anchore grype · Improper Removal of Sensitive Information Before Storage or Transfer

Affects anchore grypeSource CVE Database V5

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

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

8.2High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.104.0

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

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: High
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: High: There is a total loss of confidentiality, resulting in all resources within the Subsequent System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade anchore/grype to 0.104.0.

Affected software

Product	Affected	Fixed in
GitHubanchore/grype`pkg:github/anchore/grype`Other threats	Affected <0.104.0 >=0.68.0	Fixed in 0.104.0

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

AI-suggested

1. Immediately upgrade Anchore Grype to version 0.104.1 or later, where the vulnerability is patched. 2. Until upgrading, avoid using the --file or --output json=<file> options when running Grype scans with registry credentials; instead, redirect stdout to a file to prevent credentials from being embedded in output files. 3. Audit existing Grype output files generated with vulnerable versions for leaked credentials and rotate any exposed registry credentials promptly. 4. Implement strict access controls and encryption on storage locations containing Grype output files to minimize exposure risk. 5. Integrate secrets management solutions to avoid embedding credentials directly in scanning configurations or environment variables. 6. Review and harden CI/CD pipeline permissions to limit the impact of any leaked credentials. 7. Monitor logs and network traffic for unusual access patterns to container registries that could indicate credential misuse. 8. Educate DevOps and security teams about secure usage of vulnerability scanners and proper handling of sensitive output data.

Description

CVE-2025-65965 is a high-severity vulnerability in Anchore Grype, a container image and filesystem vulnerability scanner. Versions 0.68.0 through 0.104.0 improperly include unsanitized registry credentials in output files when using the --file or --output json=<file> options. This credential disclosure can lead to unauthorized access if output files are exposed. The vulnerability does not require authentication or user interaction and affects confidentiality with high impact. It has been patched in version 0.104.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality of container registry credentials. Leakage of these credentials could allow attackers to access private container images, potentially leading to unauthorized deployment of malicious containers, data exfiltration, or lateral movement within the network. Organizations in sectors with stringent data protection requirements, such as finance, healthcare, and critical infrastructure, could face regulatory and reputational damage if such credentials are exposed. The vulnerability affects the integrity of the container supply chain by undermining trust in vulnerability scanning processes. Additionally, compromised registry credentials could facilitate further attacks on cloud environments or CI/CD pipelines. Since Grype is commonly used in DevOps and security workflows, the scope of affected systems can be broad, impacting multiple teams and environments. The ease of exploitation without authentication increases the urgency for remediation. Overall, the vulnerability could disrupt secure container deployment practices and expose sensitive operational secrets.

CWE-212Improper Removal of Sensitive Information Before Storage or Transfer (opens in a new tab)
Base weakness
The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.
Requirements
Clearly specify which information should be regarded as private or sensitive, and require that the product offers functionality that allows the user to cleanse the sensitive information from the resource before it is published or exported to other parties.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation · Operation · Attack Surface Reduction
Some tools can automatically analyze documents to redact, strip, or "sanitize" private information, although some human review might be necessary. Tools may vary in terms of which document formats can be processed.
OWASP ASVS 4.0.3
V8.3.2 (opens in a new tab)
Attack patterns
Windows ::DATA Alternate Data Stream (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Dec 2025, 20:06 UTC

WeaknessesCWE-212

Technical details

References

Community reviews

Related threats