VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/containernetworking/cni: vulnerability history, versions and safety

github.com/containernetworking/cni is a package in the Go ecosystem. Vulert records 3 vulnerabilities for it across 120 releases, from Feb 2022 to Jul 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.

See all github.com/containernetworking/cni vulnerabilities

Vulert verdict on github.com/containernetworking/cni v1.3.1 i

Updated on 23 Oct 2026

Action needed: v1.3.1 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 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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.3.1 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 01 Jul 2022 i
  • Highest CVSS 7.2 i
  • With no published fix 0 i
  • Stars 6,139 i
  • OpenSSF scorecard 3/10 i
  • Last release 2 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/containernetworking/cni, 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.0.0-20260914164024-3ee5ddf6d892 14 Sep 2026 H1 U2 Apache-2.0 Yes Details →
v1.3.2-0.20260914164024-3ee5ddf6d892 14 Sep 2026 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20260813004707-3f51e8803ebb 13 Aug 2026 H1 U2 Apache-2.0 Yes Details →
v1.3.1 13 Aug 2026 H1 U2 Apache-2.0 Yes Details →
v1.3.1-0.20260813004707-3f51e8803ebb 13 Aug 2026 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20251215083429-7c270076995b 15 Dec 2025 H1 U2 Apache-2.0 Yes Details →
v1.3.1-0.20251215083429-7c270076995b 15 Dec 2025 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20251110152224-1d67f89a2e3c 10 Nov 2025 H1 U2 Apache-2.0 Yes Details →
v1.3.1-0.20251110152224-1d67f89a2e3c 10 Nov 2025 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20251022160428-bab140efa75f 22 Oct 2025 H1 U2 Apache-2.0 Yes Details →
v1.3.1-0.20251022160428-bab140efa75f 22 Oct 2025 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20251015082305-c5470a91d2fd 15 Oct 2025 H1 U2 Apache-2.0 Yes Details →
v1.3.1-0.20251015082305-c5470a91d2fd 15 Oct 2025 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20250901151104-c3779470b66d 01 Sep 2025 H1 U2 Apache-2.0 Yes Details →
v1.3.1-0.20250901151104-c3779470b66d 01 Sep 2025 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20250901150528-eba4f349f5e8 01 Sep 2025 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20250721152334-260917dab05c 21 Jul 2025 H1 U2 Apache-2.0 Yes Details →
v1.3.1-0.20250721152334-260917dab05c 21 Jul 2025 H1 U2 Apache-2.0 Yes Details →
v1.3.1-0.20250602151133-ee7c96f20183 02 Jun 2025 H1 U2 Apache-2.0 Yes Details →
v1.3.1-0.20250516083026-d0bdb01ee93a 16 May 2025 H1 U2 Apache-2.0 Yes Details →
v1.3.1-0.20250422214617-8338cebec23f 22 Apr 2025 H1 U2 Apache-2.0 Yes Details →
v1.3.1-0.20250414154004-277757c33328 14 Apr 2025 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20250407153753-a28faab92684 07 Apr 2025 H1 U2 Apache-2.0 Yes Details →
v1.3.0 07 Apr 2025 H1 U2 Apache-2.0 Yes Details →
v1.2.4-0.20250331141500-097592d34bb9 31 Mar 2025 H1 U2 Apache-2.0 Yes Details →
v1.2.4-0.20241007002657-370b9375346a 07 Oct 2024 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20240917141421-3b4dfc5dffa2 17 Sep 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.4-0.20240917141421-3b4dfc5dffa2 17 Sep 2024 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20240829080103-4c9ae43c0eaa 29 Aug 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.4-0.20240829080103-4c9ae43c0eaa 29 Aug 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.4-0.20240828133050-81ed2d06d6d5 28 Aug 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.4-0.20240826003946-f0289faa47c2 26 Aug 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.4-0.20240722151415-81d15e90c3d6 22 Jul 2024 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20240722151034-309b6bbc17b2 22 Jul 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.3 22 Jul 2024 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20240624195930-d5c71ad52812 24 Jun 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.2 24 Jun 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.2-0.20240624195930-d5c71ad52812 24 Jun 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.1 17 Jun 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.1-0.20240617151544-e82d9969cffe 17 Jun 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.1-0.20240610152341-ed014fe9dc27 10 Jun 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.1-0.20240528082617-cebd7dff3a97 28 May 2024 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20240513144334-1e7858f9879a 13 May 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.1-0.20240513144334-1e7858f9879a 13 May 2024 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20240513144131-c04330ee9e0b 13 May 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.1-0.20240513144131-c04330ee9e0b 13 May 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.1-0.20240506144811-f85b8fe31f60 06 May 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.1-0.20240429003911-3d7be1bae94f 29 Apr 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0 15 Apr 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1.0.20240415154708-df52e9460d3a 15 Apr 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1.0.20240415153918-047255eeed6e 15 Apr 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1.0.20240408151656-0137b3239828 08 Apr 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1.0.20240408150910-dd65e2d5275f 08 Apr 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1.0.20240405120025-bbae2202a698 05 Apr 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1.0.20240403144946-0036b628e1bf 03 Apr 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1.0.20240327154023-83287db83035 27 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1.0.20240326165740-a67dabb3d005 26 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1.0.20240325143532-951d8d0e05af 25 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1.0.20240325142803-f846cb72b0d9 25 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1.0.20240319202414-829ae61c5815 19 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20240319103633-86c37cb0a21b 19 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc0.0.20240319103633-86c37cb0a21b 19 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc1 19 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc0.0.20240318112201-56f11c6c0cc0 18 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20240317203738-a448e71e9867 17 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc0.0.20240317203738-a448e71e9867 17 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc0.0.20240315151110-1c8da137b2b7 15 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc0.0.20240312122738-563cf56c273c 12 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc0.0.20240307231245-2d04079cfe78 07 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20240305095332-845a73789a11 05 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc0.0.20240305095332-845a73789a11 05 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc0.0.20240304173223-a4d4a0d1ff21 04 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc0.0.20240304165301-06d9dec402aa 04 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc0.0.20240304164110-c822f1331bac 04 Mar 2024 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20240108164725-b62753aa2bfa 08 Jan 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20240108164725-b62753aa2bfa 08 Jan 2024 H1 U2 Apache-2.0 Yes Details →
v1.2.0-rc0 08 Jan 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20240108160011-1557aeb57c24 08 Jan 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20240108155855-8ddb290852f6 08 Jan 2024 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231218160221-d1276f1ed4bf 18 Dec 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231218155810-66c292a7c5d6 18 Dec 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231211170026-2317778d4dd3 11 Dec 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231205163452-d2bbac8e6354 05 Dec 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231204155837-2cec989c82a4 04 Dec 2023 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20231120160823-93878e65304a 20 Nov 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231120160823-93878e65304a 20 Nov 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231115090839-cf9ca9e003e6 15 Nov 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231106163419-c18965d03261 06 Nov 2023 H1 U2 Apache-2.0 Yes Details →
v0.0.0-20231023085601-5968d61a1e22 23 Oct 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231023085601-5968d61a1e22 23 Oct 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231018144532-a6eaa0114621 18 Oct 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231018054403-b7d75ff4da6c 18 Oct 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231018054338-4683716a59f8 18 Oct 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231017110229-2cfe79728dda 17 Oct 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231016152707-b15c73737eb4 16 Oct 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231013204619-e86c9ca58fe6 13 Oct 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20231002152804-743a44d40404 02 Oct 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20230807155619-f6506e215fb2 07 Aug 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20230807153719-3bbe370e680d 07 Aug 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20230720085022-4a096f6be2e6 20 Jul 2023 H1 U2 Apache-2.0 Yes Details →
v1.1.3-0.20230713222822-ca96f4ca96d8 13 Jul 2023 H1 U2 — Yes Details →
v1.1.3-0.20230713205700-a899051e444b 13 Jul 2023 H1 U2 — Yes Details →
v1.1.3-0.20230713205700-c768dcb129e1 13 Jul 2023 H1 U2 — Yes Details →
v1.1.3-0.20230710152354-622537633de4 10 Jul 2023 H1 U2 — Yes Details →
v0.0.0-20230605153024-e255525e4da2 05 Jun 2023 H1 U2 — Yes Details →
v1.1.3-0.20230605153024-e255525e4da2 05 Jun 2023 H1 U2 — Yes Details →
v1.1.3-0.20230508155503-dc0779e8cec8 08 May 2023 H1 U2 — Yes Details →
v1.1.3-0.20230421112218-15612fccaa4e 21 Apr 2023 H1 U2 — Yes Details →
v1.1.3-0.20230420122201-10ec024835e5 20 Apr 2023 H1 U2 — Yes Details →
v1.1.3-0.20230420110729-9a71f523e25c 20 Apr 2023 H1 U2 — Yes Details →
v1.1.3-0.20230314192313-f8aa587bba25 14 Mar 2023 H1 U2 — Yes Details →
v1.1.3-0.20230306153341-6626820a52c9 06 Mar 2023 H1 U2 — Yes Details →
v1.1.3-0.20230306153257-435fcb141427 06 Mar 2023 H1 U2 — Yes Details →
v0.3.1-0.20230220170501-52b1cb11a507 20 Feb 2023 H1 U2 — Yes Details →
v1.1.3-0.20230220170501-52b1cb11a507 20 Feb 2023 H1 U2 — Yes Details →
v1.1.3-0.20230213161448-d42556829e93 13 Feb 2023 H1 U2 — Yes Details →
v1.1.3-0.20230209104420-cb0d26535b23 09 Feb 2023 H1 U2 — Yes Details →
v1.1.3-0.20230206160801-0821ff55fc11 06 Feb 2023 H1 U2 — Yes Details →
v1.1.3-0.20230206011450-121798a08dcc 06 Feb 2023 H1 U2 — Yes Details →
v1.1.3-0.20230130164122-f89a8c6a3e6f 30 Jan 2023 H1 U2 — Yes Details →

The newest 120 of 1,279 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/containernetworking/cni

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-20206: containernetworking/cni improper limitation of path name 7.2 high 0.8.1 15 Feb 2022
CVE-2021-20206: containernetworking/cni Improper Limitation of Path Name N/A unrated 0.8.1 01 Jul 2022
CVE-2021-20206: Directory Traversal Vulnerability in github.com/containernetworking/cni N/A unrated 0.8.1 01 Jul 2022

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/containernetworking/cni

Is github.com/containernetworking/cni safe to use?

Vulert records 3 vulnerabilities for github.com/containernetworking/cni 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/containernetworking/cni's Vulert package health score?

Vulert scores github.com/containernetworking/cni 81/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/containernetworking/cni affected?

Yes. v1.3.1, 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/containernetworking/cni should I use?

v1.3.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/containernetworking/cni have?

3 vulnerabilities are recorded for github.com/containernetworking/cni 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/containernetworking/cni vulnerabilities disclosed?

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

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