Vulnerability Database · Go · Package report

github.com/containerd/imgcrypt: vulnerability history, versions and safety

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

i
3 vulnerabilities recorded H1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/containerd/imgcrypt v1.1.11 i

Updated on 23 Oct 2026

Action needed: v1.1.11 has 3 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 65/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v1.1.11 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 28 Apr 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 438 i
  • OpenSSF scorecard 5/10 i
  • Last release 30 months ago 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/containerd/imgcrypt, 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.2.0-rc1.0.20241024120504-0fb4a7569fa8 24 Oct 2024 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20240724013606-c091455481f6 24 Jul 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1.0.20240724013606-c091455481f6 24 Jul 2024 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20240709223013-f3769dc3e47f 09 Jul 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1.0.20240709223013-f3769dc3e47f 09 Jul 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1.0.20240709215818-b1ff2f6434a7 09 Jul 2024 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20240701171037-225e38095fa3 01 Jul 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1 01 Jul 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.12-0.20240701000858-882246a6fd23 01 Jul 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.12-0.20240622031851-6b4ba3f0628d 22 Jun 2024 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20240528203804-3ca09a2db5cd 28 May 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.12-0.20240528203804-3ca09a2db5cd 28 May 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.12-0.20240425030120-27550399fb8c 25 Apr 2024 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20240419200322-619fd33080b0 19 Apr 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.11 19 Apr 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.11-0.20240419200322-619fd33080b0 19 Apr 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.11-0.20240419195840-1839e20d5156 19 Apr 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.11-0.20240404031107-f31158950325 04 Apr 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.11-0.20240328051754-cb7e5d33ff74 28 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.11-0.20240327145114-261561143c47 27 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.11-0.20240327143542-04e37ceefedd 27 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.11-0.20240314011359-9eba5fc3f67e 14 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.10 13 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.10-0.20240312015221-a6814bff0c11 12 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.10-0.20240307234354-47481fe343bd 07 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.10-0.20240307233004-10e6b83efa91 07 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.10-0.20240131225832-33997003884d 31 Jan 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.10-0.20231228204649-85b4bab9c6f9 28 Dec 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.10-0.20231220021843-1f855f4065d5 20 Dec 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.10-0.20231218234613-5d4d0bd66216 18 Dec 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.10-0.20231121225034-fcc5cb436ddd 21 Nov 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.9 31 Oct 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.9-0.20231026011904-42c23514a571 26 Oct 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.9-0.20231026005807-1d935804d2d6 26 Oct 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.8 15 Aug 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20230815123611-0f2559e3c9bb 15 Aug 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20230706000042-7a5fb7db9b80 06 Jul 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20230616105959-be90a95e8df7 16 Jun 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20230615232127-05128698797c 15 Jun 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20230501155412-e7500301cabc 01 May 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20230330105618-cfdad3414fc9 30 Mar 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20230329234802-d50cadb5bf03 29 Mar 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20230222004011-92bd74222a2c 22 Feb 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20230219201540-1c5055514add 19 Feb 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20230216143501-9a7c29f65d5b 16 Feb 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20230130121409-8a453e8b6a0f 30 Jan 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20230130115936-12e84f51fb70 30 Jan 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20221208120308-277688a8527c 08 Dec 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20221110132028-8314a7111ef1 10 Nov 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20221110013619-16a071b983f1 10 Nov 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20221110013246-d0367e9871df 10 Nov 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20221017105736-4449cebf482c 17 Oct 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.8-0.20221016144244-b6e16db881ee 16 Oct 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.7 14 Oct 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.7-0.20221014193909-01a05dffff35 14 Oct 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.7-0.20221011003452-ea9270972e9d 11 Oct 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.7-0.20221007162422-06da359b7360 07 Oct 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.7-0.20220919132212-2c93cef1eb0b 19 Sep 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.7-0.20220919001758-07dd48dc6976 19 Sep 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.7-0.20220918205851-810cd594d9a2 18 Sep 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.7-0.20220819123901-f888c8146fcb 19 Aug 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.7-0.20220819013150-98e43be32177 19 Aug 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.7-0.20220818115817-9b2765d096ad 18 Aug 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.7-0.20220818014701-554ec9bc51ae 18 Aug 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.6 07 Jun 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.6-0.20220607230603-ec7aae54455d 07 Jun 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.6-0.20220607011535-fd230421fabc 07 Jun 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.6-0.20220607011432-5e28802f7541 07 Jun 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.6-0.20220607010711-ef8596ecba1f 07 Jun 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.6-0.20220607010159-42a32bd7cc20 07 Jun 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.6-0.20220606220902-5959e8cf6db8 06 Jun 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.6-0.20220606151427-715ba8c513d7 06 Jun 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.5 18 May 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.5-0.20220518132753-4c38f1094be2 18 May 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.5-0.20220422115040-784a5a3c0d7a 22 Apr 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.5-0.20220422012601-8abd19d902ec 22 Apr 2022 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20220422005113-5bc5ba095328 22 Apr 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.5-0.20220422005113-5bc5ba095328 22 Apr 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.5-0.20220421233611-0e5d9970419e 21 Apr 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.5-0.20220421232802-cb14b455fec9 21 Apr 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.5-0.20220421044638-8ba028dca028 21 Apr 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.5-0.20220421003317-9f08722adedb 21 Apr 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.5-0.20220420171833-0796ea171c7e 20 Apr 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.5-0.20220420170413-6eaeb4a586fe 20 Apr 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.5-0.20220420170145-9cba55fc4356 20 Apr 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4 24 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20220324160549-4b7120856cc1 24 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20220324155059-f5766549f0d7 24 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20220324111813-b47494c37409 24 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20220322211951-2efa871163e1 22 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20220322210345-7eff50ecc4f6 22 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20220322161231-f842da460337 22 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20220321135207-6fdd9818a4d8 21 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20220321135207-f4400580b658 21 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20220318173852-bc7d7f2da8e2 18 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20220318161307-d4d468487cec 18 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20220303160445-727850ffb143 03 Mar 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20220107055233-ebe9f238dbef 07 Jan 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20220106174950-3c7db10f6482 06 Jan 2022 H1 U2 Apache-2.0 Yes Details →
v1.1.4-0.20211215222723-abaa301b3240 15 Dec 2021 H1 U2 Apache-2.0 Yes Details →
v1.1.3 14 Dec 2021 H1 U2 — Yes Details →
v1.1.3-0.20211214201242-3be33eb3970e 14 Dec 2021 H1 U2 — Yes Details →
v1.1.3-0.20211214030108-6b38b7344866 14 Dec 2021 H1 U2 — Yes Details →
v1.1.3-0.20211214013825-f193f83033ac 14 Dec 2021 H1 U2 — Yes Details →
v1.1.3-0.20211119164823-3d565b5c08b1 19 Nov 2021 H1 U2 — Yes Details →
v1.1.3-0.20211119144818-f442a20718a7 19 Nov 2021 H1 U2 — Yes Details →
v1.1.3-0.20211118200144-08bdc5d7d515 18 Nov 2021 H1 U2 — Yes Details →
v1.1.3-0.20211118185519-756684aa632f 18 Nov 2021 H1 U2 — Yes Details →
v1.1.3-0.20211118164342-519a38f88a69 18 Nov 2021 H1 U2 — Yes Details →
v1.1.2-0.20211029140644-f3d97aff0072 29 Oct 2021 H1 U2 — Yes Details →
v1.1.2 29 Oct 2021 H1 U2 — Yes Details →
v1.1.2-0.20211029112521-902158d48d7a 29 Oct 2021 H1 U2 — Yes Details →
v1.1.2-0.20211029061023-fe5e256b4c36 29 Oct 2021 H1 U2 — Yes Details →
v1.1.2-0.20211004205539-527ba24dfb06 04 Oct 2021 H1 U2 — Yes Details →
v1.1.2-0.20211004204544-5ad007c93b69 04 Oct 2021 H1 U2 — Yes Details →
v1.1.2-0.20210922212325-967ee1fc62e5 22 Sep 2021 H1 U2 — Yes Details →
v1.1.2-0.20210729034251-be31719b516d 29 Jul 2021 H1 U2 — Yes Details →
v1.1.2-0.20210726222617-e36f8e5ec303 26 Jul 2021 H1 U2 — Yes Details →
v1.1.2-0.20210726213704-5945d4604840 26 Jul 2021 H1 U2 — Yes Details →
v1.1.2-0.20210720042358-a852ef447cc9 20 Jul 2021 H1 U2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/containerd/imgcrypt

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 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/containerd/imgcrypt

Is github.com/containerd/imgcrypt safe to use?

Vulert records 3 vulnerabilities for github.com/containerd/imgcrypt in Go: 0 critical, 1 high, 0 medium and 0 low, plus 2 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/containerd/imgcrypt's Vulert package health score?

Vulert scores github.com/containerd/imgcrypt 65/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).

Is the latest version of github.com/containerd/imgcrypt affected?

Yes. v1.1.11, the version you would install today, has 3 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/containerd/imgcrypt should I use?

v1.1.11 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/containerd/imgcrypt have?

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

0 vulnerabilities were recorded for github.com/containerd/imgcrypt in the last 12 months, and the oldest entry in this database dates to 28 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/containerd/imgcrypt 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/containerd/imgcrypt for upcoming vulnerabilities?

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