VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

golang-github-containers-common: vulnerability history, versions and safety

golang-github-containers-common is a package in the Debian ecosystem. Vulert records 1 vulnerability for it across 61 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
1 vulnerabilities recorded U1
i
1 with no fix published

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

See the unfixed vulnerabilities →
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.

See all golang-github-containers-common vulnerabilities

Vulert verdict on golang-github-containers-common i

Updated on 23 Oct 2026

Careful: one of the 1 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 1 vulnerability on record across 1 year, none in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 01 Oct 2024 i
  • Highest CVSS 8.2 i
  • With no published fix 1 i

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 holds for golang-github-containers-common, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
0.62.2+ds1-2 U1 No Details →
0.62.2+ds1-1 U1 No Details →
0.62.0+ds1-1 U1 No Details →
0.61.1+ds1-1 U1 No Details →
0.61.0+ds1-2 U1 No Details →
0.61.0+ds1-1 U1 No Details →
0.60.4+ds1-1 U1 No Details →
0.60.3+ds1-3 U1 No Details →
0.60.2+ds1-2 U1 No Details →
0.60.2+ds1-1 U1 No Details →
0.60.1+ds1-3 U1 No Details →
0.60.1+ds1-1 U1 No Details →
0.60.0+ds1-1 U1 No Details →
0.58.2+ds1-3 U1 No Details →
0.58.2+ds1-2 U1 No Details →
0.58.0+ds1-1 U1 No Details →
0.57.4+ds1-4 U1 No Details →
0.57.4+ds1-3 U1 No Details →
0.57.4+ds1-2 U1 No Details →
0.57.4+ds1-1 U1 No Details →
0.57.2+ds1-2 U1 No Details →
0.57.2+ds1-1 U1 No Details →
0.57.0+ds1-2 U1 No Details →
0.57.0+ds1-1 U1 No Details →
0.56.0+ds1-4 U1 No Details →
0.56.0+ds1-3 U1 No Details →
0.56.0+ds1-2 U1 No Details →
0.56.0+ds1-1 U1 No Details →
0.55.4+ds1-3 U1 No Details →
0.55.4+ds1-2 U1 No Details →
0.55.4+ds1-1 U1 No Details →
0.52.0+ds1-2 U1 No Details →
0.52.0+ds1-1 U1 No Details →
0.51.0+ds1-1 U1 No Details →
0.50.1+ds1-4 U1 No Details →
0.50.1+ds1-3 U1 No Details →
0.50.1+ds1-2 U1 No Details →
0.50.1+ds1-1 U1 No Details →
0.49.1+ds1-1 U1 No Details →
0.48.0+ds1-2 U1 No Details →
0.48.0+ds1-1 U1 No Details →
0.47.2+ds1-1 U1 No Details →
0.46.0+ds1-1 U1 No Details →
0.44.5+ds1-1 U1 No Details →
0.44.4+ds1-1 U1 No Details →
0.44.3+ds1-2 U1 No Details →
0.44.3+ds1-1 U1 No Details →
0.44.0+ds1-1 U1 No Details →
0.42.1+ds1-2 U1 No Details →
0.42.1+ds1-1 U1 No Details →
0.38.16+ds1-1 U1 No Details →
0.38.12+ds1-2 U1 No Details →
0.38.12+ds1-1 U1 No Details →
0.38.9+ds1-1 U1 No Details →
0.38.5+ds2-1 U1 No Details →
0.36.0+ds1-1 U1 No Details →
0.35.4+ds1-1 U1 No Details →
0.34.2+ds1-1 U1 No Details →
0.33.4+ds1-1 U1 No Details →
0.33.4+ds1-1+deb11u2 U1 No Details →
0.33.4+ds1-1+deb11u1 U1 No Details →

Newest 61 of 61 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for golang-github-containers-common

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Symbolic Link Exploit in golang-github-containers-common: FIPS Mode Vulnerability 8.2 high No fix published 01 Oct 2024

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 golang-github-containers-common

Is golang-github-containers-common safe to use?

Vulert records 1 vulnerabilities for golang-github-containers-common in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does golang-github-containers-common have?

1 vulnerability is recorded for golang-github-containers-common in the Debian ecosystem: 0 critical, 0 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 golang-github-containers-common vulnerabilities disclosed?

0 vulnerabilities were recorded for golang-github-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 golang-github-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 golang-github-containers-common for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the golang-github-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.