VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/quay/claircore: vulnerability history, versions and safety

github.com/quay/claircore is a package in the Go ecosystem. Vulert records 5 vulnerabilities for it across 120 releases, from Mar 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H1 M1 U3
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 17 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/quay/claircore vulnerabilities

Vulert verdict on github.com/quay/claircore v1.6.1 i

Updated on 22 Oct 2026

Careful: v1.6.1 has 5 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v1.6.1 — affected i
  • Vulnerabilities on record 5 over 4 years · 2 in the last year i
  • Latest disclosure 17 Jul 2026 i
  • Highest CVSS 7.8 i
  • With no published fix 2 i
  • Stars 154 i
  • OpenSSF scorecard 5/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/quay/claircore, 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
v1.6.2-0.20261020202705-5fced1da0e77 20 Oct 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.2-0.20261019204531-ab29b115cb67 19 Oct 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.2-0.20261016195131-476e8172dd4c 16 Oct 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.1-0.20261013175152-e2cb32484814 13 Oct 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.2-0.20261013175152-e2cb32484814 13 Oct 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.1 08 Oct 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.1-0.20261008143636-a3dbce3d3895 08 Oct 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.56 08 Oct 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.56-0.20261005175236-5971ffd8191b 05 Oct 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.1-0.20261001032238-531d0d4c986e 01 Oct 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.1-0.20260925220922-48ceddfb80ed 25 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.1-0.20260924160021-464418f71802 24 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.1-0.20260923221025-c82534e96ee7 23 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.1-0.20260921221434-4b16410062d2 21 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55 18 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260918190217-6d1103e29146 18 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260917222316-d1a9c6cfd924 17 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.1-0.20260917032413-f0c4b3ad2136 17 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.1-0.20260916195820-3902930ff815 16 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.1-0.20260914200658-5890b4d26f4d 14 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.1-0.20260914183653-5a1cca00f903 14 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.1-0.20260914164250-d0a54f247510 14 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.1-0.20260910032312-ef730ff47a23 10 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.6.0 08 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260908163025-bb49db767e1a 08 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260904212141-5b55a27dee97 04 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260903032229-10ea2074859e 03 Sep 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260827171837-a577636fe943 27 Aug 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260826171947-c5a380e486ff 26 Aug 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260825224900-1b5472421bb7 25 Aug 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260825185836-8dab50063cbc 25 Aug 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260821213546-0f12d7bc346d 21 Aug 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260820174958-54e3a08fa7b7 20 Aug 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260820040121-4b62873a6dcf 20 Aug 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260817191725-6b23c3f53e46 17 Aug 2026 H1 M1 U3 Apache-2.0 No Details →
v0.0.0-20260814222746-6c884ff2c063 14 Aug 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260814222746-6c884ff2c063 14 Aug 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260814005515-616fc8680eb0 14 Aug 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260810214608-69e467fabe27 10 Aug 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260730175441-6a2756f62fa3 30 Jul 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260730032217-c9418569caef 30 Jul 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260727192929-00f8ffe0a3f1 27 Jul 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260723193118-6cdcecee2543 23 Jul 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260722205833-31f223cbf7d5 22 Jul 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.45-0.20260722183828-4ad542109782 22 Jul 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.45-0.20260721205117-3343e48f2707 21 Jul 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.55-0.20260720230557-3f07716d8b96 20 Jul 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.54 20 Jul 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.54-0.20260717212206-3e30aeb389ec 17 Jul 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53 17 Jul 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260717161407-910c3c5ea267 17 Jul 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260709032247-11818e78d6ee 09 Jul 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260707004258-056d5d6861dc 07 Jul 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.45-0.20260629231409-82a0361e81c5 29 Jun 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260625194322-c46bb833c410 25 Jun 2026 H1 M1 U3 Apache-2.0 No Details →
v0.0.0-20260625185455-a2178084cc0c 25 Jun 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260625185455-a2178084cc0c 25 Jun 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260625143855-b8b6201bef1e 25 Jun 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260624192740-b205fc2c82ff 24 Jun 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260623202659-e6cd4c8e9962 23 Jun 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260618223519-d88e0761877d 18 Jun 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260617223827-8c73a7e20d31 17 Jun 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260612181508-5463b737ba7f 12 Jun 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.45-0.20260612075416-e018c5a585a0 12 Jun 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260610221653-8121da3e4939 10 Jun 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260609230952-c99d6521c52a 09 Jun 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260602153120-6d3a81222440 02 Jun 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260601155537-11f50838da39 01 Jun 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260529201122-f494820ca18e 29 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260528032331-6cf370c07422 28 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260527173034-3121bc06b434 27 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260521173336-aa68c874e1bf 21 May 2026 H1 M1 U3 Apache-2.0 No Details →
v0.0.0-20260520182245-f0e3cd6ec787 20 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260520182245-f0e3cd6ec787 20 May 2026 H1 M1 U3 Apache-2.0 No Details →
v0.0.0-20260520134053-2c2a14b4aa77 20 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260520134053-2c2a14b4aa77 20 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260519185540-7aa4708bc6eb 19 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260518203321-4fc46dfb9dd7 18 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260515210200-8b52d545a4c5 15 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260514155444-7f154584588d 14 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260512193359-284f819e9ef5 12 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260507211145-c395c42013dc 07 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260506174739-f99e8f9e95f7 06 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260505161948-257a50639b0a 05 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260504214556-0d6b2d57229e 04 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260501205757-5109b1d37243 01 May 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260430164753-57dac28e14a7 30 Apr 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260429165053-84d80a30e8f4 29 Apr 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260427170423-3aa077007bf1 27 Apr 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260424201146-7f0dd587cade 24 Apr 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260423184048-88f28c06e984 23 Apr 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260416032241-33b23f5c3ab7 16 Apr 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260413153702-81f5508d247d 13 Apr 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260410183351-0c4159015f2b 10 Apr 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260409221250-14549623ed81 09 Apr 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260408213833-051e0ae7e6fe 08 Apr 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260407181906-9ead7e5f68dd 07 Apr 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260406155435-68d3971cf351 06 Apr 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260403191951-f77e253298c4 03 Apr 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260402203018-c2f0b781a39b 02 Apr 2026 H1 M1 U3 Apache-2.0 No Details →
v1.5.53-0.20260330182533-134ff1a6d8b6 30 Mar 2026 H1 M1 U3 — No Details →
v1.5.53-0.20260327155133-d9b3ce48714d 27 Mar 2026 H1 M1 U3 — No Details →
v1.5.52 26 Mar 2026 H1 M1 U3 — No Details →
v1.5.50-0.20260325191516-3223b9d30ac8 25 Mar 2026 H1 M1 U3 — No Details →
v1.5.50-0.20260324194437-ca66b00cf2f3 24 Mar 2026 H1 M1 U3 — No Details →
v1.5.50-0.20260324165227-d6d26d236754 24 Mar 2026 H1 M1 U3 — No Details →
v1.5.51 24 Mar 2026 H1 M1 U3 — No Details →
v1.5.50-0.20260323032245-9f012381025f 23 Mar 2026 H1 M1 U3 — No Details →
v1.5.50-0.20260320195514-91c124f5f82c 20 Mar 2026 H1 M1 U3 — No Details →
v1.5.50-0.20260315080417-0e3e83c25f13 15 Mar 2026 H1 M1 U3 — No Details →
v1.5.50-0.20260312210324-6f208cd4fe7a 12 Mar 2026 H1 M1 U3 — No Details →
v1.5.50-0.20260309032304-98c1f27890a4 09 Mar 2026 H1 M1 U3 — No Details →
v1.5.50-0.20260305154959-a18dc89efa92 05 Mar 2026 H1 M1 U3 — No Details →
v1.5.50-0.20260302215435-46450a76ba70 02 Mar 2026 H1 M1 U3 — No Details →
v1.5.50 02 Mar 2026 H1 M1 U3 — No Details →
v1.5.50-0.20260302032243-22e7628bf6b9 02 Mar 2026 H1 M1 U3 — No Details →
v1.5.50-0.20260227184810-fed59758400d 27 Feb 2026 H1 M1 U3 — No Details →
v1.5.50-0.20260226183711-907771a0953b 26 Feb 2026 H1 M1 U3 — No Details →
v1.5.50-0.20260224223703-7cdf304f1478 24 Feb 2026 H1 M1 U3 — No Details →
v1.5.50-0.20260223184613-1a78a0ae5854 23 Feb 2026 H1 M1 U3 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/quay/claircore

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-3762: Path Traversal Vulnerability in claircore 7.8 high 0.4.8 04 Mar 2022
CVE-2026-10517: Claircore Unauthenticated SSRF Vulnerability Exposing Internal Services 5.8 medium No fix published 01 Jun 2026
CVE-2021-3762: Path Traversal in claircore N/A unrated 1.1.0 15 Jul 2022
CVE-2021-3762: Path traversal vulnerability in github.com/quay/claircore N/A unrated 1.1.0 15 Jul 2022
CVE-2026-10517: Claircore Unauthenticated Manifest Submission Vulnerability N/A unrated No fix published 17 Jul 2026

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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/quay/claircore

Is github.com/quay/claircore safe to use?

Vulert records 5 vulnerabilities for github.com/quay/claircore in Go: 0 critical, 1 high, 1 medium and 0 low, plus 3 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is github.com/quay/claircore's Vulert package health score?

Vulert scores github.com/quay/claircore 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/quay/claircore affected?

Yes. v1.6.1, the version you would install today, has 5 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of github.com/quay/claircore should I use?

v1.6.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/quay/claircore have?

5 vulnerabilities are recorded for github.com/quay/claircore in the Go ecosystem: 0 critical, 1 high, 1 medium and 0 low, plus 3 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/quay/claircore vulnerabilities disclosed?

2 vulnerabilities were recorded for github.com/quay/claircore in the last 12 months, and the oldest entry in this database dates to 04 Mar 2022. 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/quay/claircore 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/quay/claircore for upcoming vulnerabilities?

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