{"answers":{"affected":"3 open source packages ship an affected version, including github.com/anchore/grype.","exploited":"There is no known exploitation of CVE-2025-65965 in the wild and no public exploit code.","fix":"Upgrade github.com/anchore/grype to 0.104.1 or later.","what":"CVE-2025-65965 is a high-severity vulnerability in anchore grype, published on 25 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-65965 and fix it if it is affected.\n\nWhat it is: CVE-2025-65965 is a high-severity vulnerability in anchore grype, published on 25 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-65965 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/anchore/grype (Go): affected from 0.68.0; fixed in 0.104.1\n- github.com/anchore/grype (Go): affected from 0.68.0; fixed in 0.104.1\n- github.com/anchore/grype (Go): affected from 0.68.0; fixed in 0.104.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-65965/ (Markdown: https://insights.sbomify.com/CVE-2025-65965/index.md)","id":"CVE-2025-65965","markdown":"https://insights.sbomify.com/CVE-2025-65965/index.md","name":"CVE-2025-65965","record":{"aliases":["BELL-CVE-2025-65965","GHSA-6gxw-85q2-q646","GO-2025-4160","MINI-9mwm-3m23-xfh5"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Container vulnerability scanner","requires_auth":"none","summary":"Grype leaks registry credentials in JSON output files when specific output options are used, exposing sensitive authentication data to anyone with file access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-212","name":"Improper Removal of Sensitive Information Before Storage or Transfer"}],"description":"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=\u003cfile\u003e 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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Grype has a credential disclosure vulnerability in Grype JSON output","id":"CVE-2025-65965","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":3,"n_references":3,"next":{"headline":"OneUptime Unauthorized User Creation via API","id":"CVE-2025-65966"},"packages":[{"ecosystem":"Go","fixed":["0.104.1"],"introduced":["0.68.0"],"last_affected":[],"package":"github.com/anchore/grype","purl":null,"source":"GHSA-6gxw-85q2-q646"},{"ecosystem":"Go","fixed":["0.104.1"],"introduced":["0.68.0"],"last_affected":[],"package":"github.com/anchore/grype","purl":"pkg:golang/github.com/anchore/grype","source":"GHSA-6gxw-85q2-q646"},{"ecosystem":"Go","fixed":["0.104.1"],"introduced":["0.68.0"],"last_affected":[],"package":"github.com/anchore/grype","purl":"pkg:golang/github.com/anchore/grype","source":"GO-2025-4160"}],"prev":{"headline":"n8n Vulnerable to Remote Code Execution via Git Node Custom Pre-Commit Hook","id":"CVE-2025-65964"},"products":["grype"],"published":"2025-11-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-25","vendors":["anchore"]},"summary":"Grype leaks registry credentials in JSON output files when specific output options are used, exposing sensitive authentication data to anyone with file access.","url":"https://insights.sbomify.com/CVE-2025-65965/"}