Approved changes feed: RSS · Atom
cpe:2.3:a:anchore:grype:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Anchore (8c661697-2119-5958-a5c4-8cd8ec010026) |
|---|---|
| Product | Grype (3f6e0099-717b-5040-b27a-c17f73cc49bf) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-65965 |
vulnerable | 2026-06-08 07:39:21.106112 |
Grype has a credential disclosure vulnerability in Grype JSON output
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.
Published: 2025-11-25T19:36:11.090Z
Updated: 2025-11-25T20:08:48.709Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.