Vulnerability Database · Go · github.com/quay/claircore · Version
github.com/quay/claircore v1.5.50-0.20260324194437-ca66b00cf2f3
v1.5.50-0.20260324194437-ca66b00cf2f3 is affected by 5 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: v1.6.1.
Critical 0 High 1 Medium 1 Low 0 Unrated 3
-
Released 24 Mar 2026
Licence Apache-2.0
Also known from other sources 0
Newer releases 300
Database updated 23/Oct/2026
Release and licence data published by the Go module proxy. 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 Vulnerabilities affecting this version
github.com/quay/claircore v1.5.50-0.20260324194437-ca66b00cf2f3 vulnerabilities
5 vulnerabilities cover github.com/quay/claircore v1.5.50-0.20260324194437-ca66b00cf2f3. Open the full list 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-2026-10517: Claircore Unauthenticated Manifest Submission Vulnerability | N/A unrated | No fix published | 17 Jul 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 |
Looking for another version, or everything Vulert holds for github.com/quay/claircore?
Questions
About github.com/quay/claircore v1.5.50-0.20260324194437-ca66b00cf2f3
Is github.com/quay/claircore v1.5.50-0.20260324194437-ca66b00cf2f3 vulnerable?
Yes. 5 vulnerabilities in the Vulert database cover github.com/quay/claircore v1.5.50-0.20260324194437-ca66b00cf2f3: 0 critical, 1 high, 1 medium and 0 low, plus 3 not yet rated. The upgrade Vulert recommends is v1.6.1, and each entry above names the fixed version to move to.
Which version of github.com/quay/claircore should I use instead of v1.5.50-0.20260324194437-ca66b00cf2f3?
v1.6.1 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is v1.5.50-0.20260324194437-ca66b00cf2f3 the latest release of github.com/quay/claircore?
No. v1.5.50-0.20260324194437-ca66b00cf2f3 was published 24 Mar 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
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.