Vulnerability Database · Go · Package report

github.com/containers/common: vulnerability history, versions and safety

github.com/containers/common is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, first recorded in Oct 2024. 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 M1 U1
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/containers/common v0.64.2 i

Updated on 23 Oct 2026

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

Package health score 71/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 v0.64.2 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 14 Oct 2024 i
  • Highest CVSS 5.4 i
  • With no published fix 0 i
  • Stars 248 i
  • OpenSSF scorecard 4/10 i
  • Last release 13 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/containers/common, 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.64.2 02 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.2-0.20250827120833-a5ccdae846b6 27 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.2-0.20250826074712-7692941ae9c8 26 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.2-0.20250825133128-f437c58aab67 25 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.2-0.20250821102851-54971400010f 21 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.2-0.20250820175223-ab7a44480b3a 20 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250819102335-dad1a10ad868 19 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250814143857-1c6819688713 14 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250814094459-a7f868d8fb31 14 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250811140415-6f98aea06fcd 11 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250808104954-b6f9a443dc4b 08 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250807165115-37f07334fb2e 07 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250807090203-59e76192840d 07 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250806164630-57def9601f3b 06 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1 04 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250804093147-26d3ffcea155 04 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250801152730-233060ea1b6a 01 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250730164627-1c421c0649f2 30 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250725102636-809d42696d7c 25 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250723180346-09fb862b0ddc 23 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250722090715-778fd271ffe7 22 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250717192942-9c21c35110df 17 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.1-0.20250716222108-6df5b01c2ea6 16 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.64.0 16 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.2-0.20250715093516-b7ddbf005e32 15 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.2-0.20250711144526-f3f68c4e79f5 11 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.2-0.20250710101909-1a89ee3f9315 10 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.2-0.20250707185859-2b4e95a951de 07 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.2-0.20250704085003-074a6e0b96e0 04 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.2-0.20250701090630-c156ac84320e 01 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.2-0.20250630085511-f1e5103afb9b 30 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.2-0.20250627125909-bed7a8b142a3 27 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.2-0.20250626105023-8003ce3192de 26 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.2-0.20250624163146-1bc9d1737003 24 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.2-0.20250619110336-d638ae9ccc5e 19 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.2-0.20250606094353-2d2b7a488601 06 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.2-0.20250606005824-e06bb9f9d6e9 06 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.2-0.20250604184922-bb2062b6265c 04 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.1 03 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.1-0.20250602154905-5a4ca2d5d355 02 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.1-0.20250528122446-1a3b5ecec62f 28 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.1-0.20250516182445-01126e4256a5 16 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.1-0.20250512121019-54b90177af76 12 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.1-0.20250506090306-a9589cf6825e 06 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.1-0.20250505154152-f15bcef1a4fe 05 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.1-0.20250502102457-8c556c45bf9d 02 May 2025 M1 U1 Apache-2.0 Yes Details →
v0.55.5-0.20250430094630-83d82c09b50e 30 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.1-0.20250428155145-82737eba32a1 28 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.1-0.20250424100100-2c4f52ff67c0 24 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.1-0.20250422183953-ffbac5eae3a2 22 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.1-0.20250417134300-bb92ade2bafa 17 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.63.0 16 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.4-0.20250415170104-e8ccfbf9d99e 15 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.4-0.20250414094938-62f5c9fcc507 14 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.4-0.20250413101530-d4ac0ba50ed0 13 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.4-0.20250411145332-dd8ab77b8e26 11 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.4-0.20250409185557-f71a7a6eca1d 09 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.4-0.20250407140031-6260b5fe114c 07 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.4-0.20250403135752-95a74821d55e 03 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.55.5-0.20250403130720-5f05bf794d17 03 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.4-0.20250401165412-9b0d134f392f 01 Apr 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.4-0.20250328183545-93c5bc8305b6 28 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3-0.20250327190718-8b6a29c10df7 27 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3 27 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3-0.20250327090809-720479cd1bc7 27 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3-0.20250326180846-954a8ceee5a2 26 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3-0.20250326101258-442957aa798d 26 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3-0.20250325181554-ff2f761a48f9 25 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3-0.20250324165222-5a6b03519704 24 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3-0.20250324121725-e360699fb3e3 24 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3-0.20250321171839-dbeb17e40c80 21 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3-0.20250320215058-fa53559b5062 20 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3-0.20250320194714-8f76077421cc 20 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3-0.20250320113334-33bf9345b5ef 20 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3-0.20250318135859-a56094c5fea0 18 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3-0.20250314112710-e5dd907879d9 14 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3-0.20250313141947-9c66f4529890 13 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.3-0.20250312184844-faf4577d50af 12 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.2-0.20250312105408-1525f570b6ce 12 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.2-0.20250311121556-b27979403716 11 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.2 10 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.2-0.20250310170903-09fe0ef7168d 10 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20250306142925-6e82793fd29d 06 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.2-0.20250306142925-6e82793fd29d 06 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.2-0.20250305132755-84419f687c90 05 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.2-0.20250304201245-7b93145d0ebb 04 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.1-0.20250303103139-de1bf042763c 03 Mar 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.1 28 Feb 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.1-0.20250228144942-bdb341859870 28 Feb 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.1-0.20250226181419-2a87cccd1d5d 26 Feb 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.1-0.20250218102854-3c510166fd85 18 Feb 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.1-0.20250217155304-b4923052a36a 17 Feb 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.1-0.20250214103326-1e4c9bf42bd5 14 Feb 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.1-0.20250213173827-a9930714b554 13 Feb 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.1-0.20250208131654-13efd7839dde 08 Feb 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.1-0.20250204174743-942318311541 04 Feb 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.1-0.20250203191257-f1e8882b9e98 03 Feb 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.1-0.20250131220801-3a494c638780 31 Jan 2025 M1 U1 Apache-2.0 Yes Details →
v0.62.0 31 Jan 2025 M1 U1 Apache-2.0 Yes Details →
v0.61.1-0.20250130155051-828e98ca78d2 30 Jan 2025 M1 U1 Apache-2.0 Yes Details →
v0.61.1-0.20250124131345-fa339b6b6eda 24 Jan 2025 M1 U1 — Yes Details →
v0.61.1-0.20250121185748-34a90afcdc6d 21 Jan 2025 M1 U1 — Yes Details →
v0.61.1-0.20250120135258-06628cb958e9 20 Jan 2025 M1 U1 — Yes Details →
v0.61.1 15 Jan 2025 M1 U1 — Yes Details →
v0.61.1-0.20250113165907-a0fde92acb71 13 Jan 2025 M1 U1 — Yes Details →
v0.61.1-0.20250109101513-03380ecd72b0 09 Jan 2025 M1 U1 — Yes Details →
v0.61.1-0.20250108191018-67c458b4a286 08 Jan 2025 M1 U1 — Yes Details →
v0.61.1-0.20250106142059-514bf04d8e6a 06 Jan 2025 M1 U1 — Yes Details →
v0.61.1-0.20241217130428-4ddb12022b16 17 Dec 2024 M1 U1 — Yes Details →
v0.61.1-0.20241211190400-a56e85d51c4e 11 Dec 2024 M1 U1 — Yes Details →
v0.61.1-0.20241210175044-6b3982794c89 10 Dec 2024 M1 U1 — Yes Details →
v0.61.1-0.20241209143419-36a929ed80fb 09 Dec 2024 M1 U1 — Yes Details →
v0.61.1-0.20241206191610-a2b7fc094f81 06 Dec 2024 M1 U1 — Yes Details →
v1.0.2-0.20241206191610-a2b7fc094f81 06 Dec 2024 M1 U1 — Yes Details →
v0.61.1-0.20241206111608-6653a8c6a705 06 Dec 2024 M1 U1 — Yes Details →
v1.0.2-0.20241206111608-6653a8c6a705 06 Dec 2024 M1 U1 — Yes Details →
v0.61.1-0.20241205133410-324d16622576 05 Dec 2024 M1 U1 — Yes Details →
v1.0.2-0.20241205133410-324d16622576 05 Dec 2024 M1 U1 — Yes Details →
v0.61.1-0.20241204184723-34b9d0d4cd7a 04 Dec 2024 M1 U1 — Yes Details →
v1.0.2-0.20241204184723-34b9d0d4cd7a 04 Dec 2024 M1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/containers/common

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/containers/common

Is github.com/containers/common safe to use?

Vulert records 2 vulnerabilities for github.com/containers/common in Go: 0 critical, 0 high, 1 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/containers/common's Vulert package health score?

Vulert scores github.com/containers/common 71/100, which reads as in good shape. 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/containers/common affected?

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

Which version of github.com/containers/common should I use?

v0.64.2 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/containers/common have?

2 vulnerabilities are recorded for github.com/containers/common in the Go ecosystem: 0 critical, 0 high, 1 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/containers/common vulnerabilities disclosed?

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

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