Vulnerability Database · Go · Package report

github.com/anchore/grype: vulnerability history, versions and safety

github.com/anchore/grype is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 0 release, first recorded in Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 25 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/anchore/grype v0.121.0 i

Updated on 23 Oct 2026

Good news: v0.121.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 88/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

What to do: Stay on v0.121.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.121.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v0.121.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 25 Nov 2025 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Stars 13,045 i
  • OpenSSF scorecard 7/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/anchore/grype, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.121.1-0.20261022151616-e196e95d3fcb 22 Oct 2026 none Apache-2.0 — Details →
v0.121.1-0.20261022131909-c5c9674cccde 22 Oct 2026 none Apache-2.0 — Details →
v0.120.2-0.20261019193712-afe2742527d9 19 Oct 2026 none Apache-2.0 — Details →
v0.121.0 19 Oct 2026 none Apache-2.0 — Details →
v0.120.2-0.20261019054407-9c6c9d1a7c40 19 Oct 2026 none Apache-2.0 — Details →
v0.120.2-0.20261016202517-8ea928e9f642 16 Oct 2026 none Apache-2.0 — Details →
v0.120.2-0.20261015112118-a402503ab977 15 Oct 2026 none Apache-2.0 — Details →
v0.120.2-0.20261013173532-3e20d69159df 13 Oct 2026 none Apache-2.0 — Details →
v0.120.2-0.20261012204034-c8b8c3773e78 12 Oct 2026 none Apache-2.0 — Details →
v0.120.2-0.20261009162927-e3e89ac36773 09 Oct 2026 none Apache-2.0 — Details →
v0.120.2-0.20261009161348-e00511bc458c 09 Oct 2026 none Apache-2.0 — Details →
v0.120.2-0.20261008131403-5dbdab183e88 08 Oct 2026 none Apache-2.0 — Details →
v0.120.1 06 Oct 2026 none Apache-2.0 — Details →
v0.120.1-0.20261005192153-68afe99d5f51 05 Oct 2026 none Apache-2.0 — Details →
v0.120.1-0.20261002141223-4759e3962778 02 Oct 2026 none Apache-2.0 — Details →
v0.120.0 02 Oct 2026 none Apache-2.0 — Details →
v0.119.1-0.20261001214514-2756979af930 01 Oct 2026 none Apache-2.0 — Details →
v0.119.1-0.20261001195615-8ba5f6933bf8 01 Oct 2026 none Apache-2.0 — Details →
v0.119.1-0.20261001134225-21d07162b427 01 Oct 2026 none Apache-2.0 — Details →
v0.119.1-0.20260930185717-1112002c60a3 30 Sep 2026 none Apache-2.0 — Details →
v0.119.1-0.20260929160921-9efa4578d97c 29 Sep 2026 none Apache-2.0 — Details →
v0.119.1-0.20260928055734-8880097c93fb 28 Sep 2026 none Apache-2.0 — Details →
v0.119.1-0.20260925200940-c24afc3a5e23 25 Sep 2026 none Apache-2.0 — Details →
v0.119.1-0.20260925104902-c3b9218ff296 25 Sep 2026 none Apache-2.0 — Details →
v0.119.1-0.20260924150829-833933d9d769 24 Sep 2026 none Apache-2.0 — Details →
v0.119.1-0.20260918155950-41a43d8a85c1 18 Sep 2026 none Apache-2.0 — Details →
v0.119.1-0.20260918010033-098c1c90c80f 18 Sep 2026 none Apache-2.0 — Details →
v0.119.0 17 Sep 2026 none Apache-2.0 — Details →
v0.118.1-0.20260917124947-fd587700b2e6 17 Sep 2026 none Apache-2.0 — Details →
v0.0.0-20260916150318-5d59278f6ff6 16 Sep 2026 none Apache-2.0 — Details →
v0.118.1-0.20260916150318-5d59278f6ff6 16 Sep 2026 none Apache-2.0 — Details →
v0.118.1-0.20260914212632-28a39f729fe0 14 Sep 2026 none Apache-2.0 — Details →
v0.118.1-0.20260911160427-bf5f48bf540e 11 Sep 2026 none Apache-2.0 — Details →
v0.118.1-0.20260911004237-d1a52b35bcc6 11 Sep 2026 none Apache-2.0 — Details →
v0.118.1-0.20260909155645-b6956748f419 09 Sep 2026 none Apache-2.0 — Details →
v0.118.1-0.20260909012042-27c95c966179 09 Sep 2026 none Apache-2.0 — Details →
v0.118.1-0.20260908153358-4b519cbd5113 08 Sep 2026 none Apache-2.0 — Details →
v0.118.1-0.20260904160234-65ec52e70a37 04 Sep 2026 none Apache-2.0 — Details →
v0.118.1-0.20260902090746-0f37e38fac6c 02 Sep 2026 none Apache-2.0 — Details →
v0.118.1-0.20260828215524-f6f2ce0a2293 28 Aug 2026 none Apache-2.0 — Details →
v0.118.1-0.20260828155901-999b656f33df 28 Aug 2026 none Apache-2.0 — Details →
v0.118.1-0.20260827203739-cc624ba4a45d 27 Aug 2026 none Apache-2.0 — Details →
v0.117.1-0.20260827184029-756eb9a24f7b 27 Aug 2026 none Apache-2.0 — Details →
v0.118.0 27 Aug 2026 none Apache-2.0 — Details →
v0.117.1-0.20260827150645-9963eb738b01 27 Aug 2026 none Apache-2.0 — Details →
v0.117.1-0.20260826193934-8b1354cff9c7 26 Aug 2026 none Apache-2.0 — Details →
v0.117.1-0.20260825224740-0f57388ec805 25 Aug 2026 none Apache-2.0 — Details →
v0.117.1-0.20260821160051-ab6707d1d575 21 Aug 2026 none Apache-2.0 — Details →
v0.117.1-0.20260814155136-ffbca561d576 14 Aug 2026 none Apache-2.0 — Details →
v0.117.0 10 Aug 2026 none Apache-2.0 — Details →
v0.116.2-0.20260809050734-31c8fa181ada 09 Aug 2026 none Apache-2.0 — Details →
v0.116.2-0.20260807155835-709e090289cd 07 Aug 2026 none Apache-2.0 — Details →
v0.116.2-0.20260803144731-970b4d102886 03 Aug 2026 none Apache-2.0 — Details →
v0.116.2-0.20260731155716-f8e0d226de81 31 Jul 2026 none Apache-2.0 — Details →
v0.116.2-0.20260730165742-36970a7a8d07 30 Jul 2026 none Apache-2.0 — Details →
v0.116.1 28 Jul 2026 none Apache-2.0 — Details →
v0.116.1-0.20260727150833-545d91432e40 27 Jul 2026 none Apache-2.0 — Details →
v0.116.1-0.20260727141543-ba11c44c7eea 27 Jul 2026 none Apache-2.0 — Details →
v0.116.1-0.20260724155557-072fe5938e2b 24 Jul 2026 none Apache-2.0 — Details →
v0.116.1-0.20260722144620-4562c55cebba 22 Jul 2026 none Apache-2.0 — Details →
v0.116.1-0.20260721135229-44ad33fa0630 21 Jul 2026 none Apache-2.0 — Details →
v0.116.1-0.20260720153233-ea5e99ae6581 20 Jul 2026 none Apache-2.0 — Details →
v0.116.1-0.20260717162047-5917fe588250 17 Jul 2026 none Apache-2.0 — Details →
v0.116.1-0.20260716220826-1c7b51400bfc 16 Jul 2026 none Apache-2.0 — Details →
v0.0.0-20260716160215-3b014b00097d 16 Jul 2026 none Apache-2.0 — Details →
v0.116.0 16 Jul 2026 none Apache-2.0 — Details →
v0.115.1-0.20260715192723-159bf2d7c2d3 15 Jul 2026 none Apache-2.0 — Details →
v0.115.1-0.20260715144227-fcf08ae0a418 15 Jul 2026 none Apache-2.0 — Details →
v0.115.1-0.20260713131914-bcfc0e7a0833 13 Jul 2026 none Apache-2.0 — Details →
v0.115.1-0.20260710155941-b31a42222f9e 10 Jul 2026 none Apache-2.0 — Details →
v0.115.1-0.20260709200408-ea623611ad36 09 Jul 2026 none Apache-2.0 — Details →
v0.115.1-0.20260709194242-1c601b264949 09 Jul 2026 none Apache-2.0 — Details →
v0.115.1-0.20260709151745-7d9e2ec5e2a2 09 Jul 2026 none Apache-2.0 — Details →
v0.115.1-0.20260708183617-fc88fade29f0 08 Jul 2026 none Apache-2.0 — Details →
v0.115.1-0.20260703162201-67ba7a178df4 03 Jul 2026 none Apache-2.0 — Details →
v0.115.1-0.20260702190413-d4b3a5f6a361 02 Jul 2026 none Apache-2.0 — Details →
v0.115.1-0.20260626155356-c41e34d136d9 26 Jun 2026 none Apache-2.0 — Details →
v0.114.1-0.20260626101627-fa8b7e2a528c 26 Jun 2026 none Apache-2.0 — Details →
v0.115.0 26 Jun 2026 none Apache-2.0 — Details →
v0.114.1-0.20260625161010-095cea96784a 25 Jun 2026 none Apache-2.0 — Details →
v0.0.0-20260624032646-219a3b808f03 24 Jun 2026 none Apache-2.0 — Details →
v0.114.1-0.20260624032646-219a3b808f03 24 Jun 2026 none Apache-2.0 — Details →
v0.114.1-0.20260623163040-fa5977bd05eb 23 Jun 2026 none Apache-2.0 — Details →
v0.114.1-0.20260622204551-80c4dcbf25e3 22 Jun 2026 none Apache-2.0 — Details →
v0.114.1-0.20260619155509-7e7b75f4a985 19 Jun 2026 none Apache-2.0 — Details →
v0.114.1-0.20260618215842-d6dae9d36dcf 18 Jun 2026 none Apache-2.0 — Details →
v0.114.1-0.20260618194122-70d0100826b0 18 Jun 2026 none Apache-2.0 — Details →
v0.114.1-0.20260616131428-55b3304bcd0e 16 Jun 2026 none Apache-2.0 — Details →
v0.114.1-0.20260615131603-3888f9b7139e 15 Jun 2026 none Apache-2.0 — Details →
v0.114.1-0.20260612155630-f54a905415fb 12 Jun 2026 none Apache-2.0 — Details →
v0.114.1-0.20260609173954-77bf6acbbbe4 09 Jun 2026 none Apache-2.0 — Details →
v0.114.0 05 Jun 2026 none Apache-2.0 — Details →
v0.113.1-0.20260604203350-024e26b9c93c 04 Jun 2026 none Apache-2.0 — Details →
v0.113.1-0.20260603160810-7e47096960cb 03 Jun 2026 none Apache-2.0 — Details →
v0.113.0 03 Jun 2026 none Apache-2.0 — Details →
v0.112.1-0.20260602210504-577c4cd6e4f8 02 Jun 2026 none Apache-2.0 — Details →
v0.112.1-0.20260602152937-1a5ef89bbf52 02 Jun 2026 none Apache-2.0 — Details →
v0.112.1-0.20260602013846-a1ee6b42e183 02 Jun 2026 none Apache-2.0 — Details →
v0.112.1-0.20260529190443-075eed9f2457 29 May 2026 none Apache-2.0 — Details →
v0.112.1-0.20260526013349-4f57d03014f6 26 May 2026 none Apache-2.0 — Details →
v0.112.1-0.20260522155837-82044d54c18d 22 May 2026 none — — Details →
v0.112.1-0.20260521222519-c306be24b0a2 21 May 2026 none — — Details →
v0.112.1-0.20260520150108-a345ece29f37 20 May 2026 none — — Details →
v0.112.1-0.20260519163405-e760f4a5fbfc 19 May 2026 none — — Details →
v0.112.1-0.20260518192050-95573073808c 18 May 2026 none — — Details →
v0.112.1-0.20260515155804-82d4c7a95f62 15 May 2026 none — — Details →
v0.112.1-0.20260513180549-03cbb5f8457c 13 May 2026 none — — Details →
v0.112.1-0.20260512173804-3d0e03b4864e 12 May 2026 none — — Details →
v0.112.1-0.20260511202244-14dc722c8285 11 May 2026 none — — Details →
v0.112.1-0.20260509161657-7b26aa2aa406 09 May 2026 none — — Details →
v0.112.1-0.20260508210308-70459ffae478 08 May 2026 none — — Details →
v0.112.1-0.20260507165716-ffc0abfef07f 07 May 2026 none — — Details →
v0.112.1-0.20260505154157-e149729cfd11 05 May 2026 none — — Details →
v0.112.1-0.20260504205318-3154f4936281 04 May 2026 none — — Details →
v0.112.1-0.20260504141325-58d8013dc703 04 May 2026 none — — Details →
v0.112.1-0.20260501214136-51d0be5d3738 01 May 2026 none — — Details →
v0.112.0 01 May 2026 none — — Details →
v0.111.2-0.20260430142623-d646a935cd1b 30 Apr 2026 none — — Details →
v0.111.2-0.20260429132220-d11ee91c8a30 29 Apr 2026 none — — Details →
v0.111.2-0.20260424155543-6d0b66c527ee 24 Apr 2026 none — — Details →

The newest 120 of 952 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/anchore/grype

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/anchore/grype

Is github.com/anchore/grype safe to use?

Vulert records 2 vulnerabilities for github.com/anchore/grype in Go: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/anchore/grype's Vulert package health score?

Vulert scores github.com/anchore/grype 88/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/anchore/grype affected?

No. v0.121.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does github.com/anchore/grype have?

2 vulnerabilities are recorded for github.com/anchore/grype in the Go ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/anchore/grype vulnerabilities disclosed?

2 vulnerabilities were recorded for github.com/anchore/grype in the last 12 months, and the oldest entry in this database dates to 25 Nov 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/anchore/grype are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/anchore/grype for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/anchore/grype version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.