VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/checkpoint-restore/go-criu/v7: vulnerability history, versions and safety

github.com/checkpoint-restore/go-criu/v7 is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

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/checkpoint-restore/go-criu/v7 vulnerabilities

Vulert verdict on github.com/checkpoint-restore/go-criu/v7 v7.2.0 i

Updated on 23 Oct 2026

Good news: v7.2.0, the version you would install today, has no known vulnerabilities.

Package health score 62/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

What to do: Stay on v7.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v7.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v7.2.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 253 i
  • OpenSSF scorecard 5/10 i
  • Last release 25 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/checkpoint-restore/go-criu/v7, 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
v7.0.0-20250606160457-5d78d817d554 06 Jun 2025 none Apache-2.0 — Details →
v7.2.1-0.20250606160457-5d78d817d554 06 Jun 2025 none Apache-2.0 — Details →
v7.2.1-0.20250605151100-9e012ba02db6 05 Jun 2025 none Apache-2.0 — Details →
v7.2.1-0.20250531120011-cc60bab76961 31 May 2025 none Apache-2.0 — Details →
v7.2.1-0.20250530185312-162811233b63 30 May 2025 none Apache-2.0 — Details →
v7.2.1-0.20250501132539-e26f3eae6b1e 01 May 2025 none Apache-2.0 — Details →
v7.2.1-0.20250328164923-a3d9050ffd65 28 Mar 2025 none Apache-2.0 — Details →
v7.2.1-0.20250328072524-d246c3dc0b34 28 Mar 2025 none Apache-2.0 — Details →
v7.2.1-0.20250304171349-bebbf96c34ac 04 Mar 2025 none Apache-2.0 — Details →
v7.2.1-0.20250114113409-9996dd52bbd0 14 Jan 2025 none Apache-2.0 — Details →
v7.2.1-0.20250107172645-b9d8fadc19b8 07 Jan 2025 none Apache-2.0 — Details →
v7.2.1-0.20250107120404-47757dcf3313 07 Jan 2025 none Apache-2.0 — Details →
v7.1.1-0.20240909093043-39135d0112fa 09 Sep 2024 none Apache-2.0 — Details →
v7.2.0 09 Sep 2024 none Apache-2.0 — Details →
v7.1.1-0.20240908115727-1353c6839aff 08 Sep 2024 none Apache-2.0 — Details →
v7.1.1-0.20240901175100-3b1e16a1250b 01 Sep 2024 none Apache-2.0 — Details →
v7.1.1-0.20240728160228-a9064d7e053c 28 Jul 2024 none Apache-2.0 — Details →
v7.1.1-0.20240728084016-20dfec875cfe 28 Jul 2024 none Apache-2.0 — Details →
v7.1.1-0.20240723071257-2dd9980e77c3 23 Jul 2024 none Apache-2.0 — Details →
v7.1.1-0.20240717102439-664a3fddda7d 17 Jul 2024 none Apache-2.0 — Details →
v7.1.1-0.20240715222910-227a6b784915 15 Jul 2024 none Apache-2.0 — Details →
v7.1.1-0.20240705130549-3b91d77dfa8a 05 Jul 2024 none Apache-2.0 — Details →
v7.1.1-0.20240701130400-4c515e0a7289 01 Jul 2024 none Apache-2.0 — Details →
v7.1.1-0.20240603055151-ae18f4225e2e 03 Jun 2024 none Apache-2.0 — Details →
v7.1.1-0.20240601130338-15f2229742f6 01 Jun 2024 none Apache-2.0 — Details →
v7.1.1-0.20240502061215-c05d4c25be02 02 May 2024 none Apache-2.0 — Details →
v7.1.1-0.20240501132715-a294620b2089 01 May 2024 none Apache-2.0 — Details →
v7.0.1-0.20240315074411-972bd31ea112 15 Mar 2024 none Apache-2.0 — Details →
v7.1.0 15 Mar 2024 none Apache-2.0 — Details →
v7.0.1-0.20240314122426-0327d417f071 14 Mar 2024 none Apache-2.0 — Details →
v7.0.1-0.20240304140711-5d0d8f1eb21b 04 Mar 2024 none Apache-2.0 — Details →
v7.0.0-20240115170647-771e3d7e5740 15 Jan 2024 none Apache-2.0 — Details →
v7.0.1-0.20240115170647-771e3d7e5740 15 Jan 2024 none Apache-2.0 — Details →
v7.0.1-0.20231228211859-57bdacdb325d 28 Dec 2023 none Apache-2.0 — Details →
v7.0.1-0.20231221080006-d163ebf339a0 21 Dec 2023 none Apache-2.0 — Details →
v7.0.1-0.20231202104646-251fa2e32de5 02 Dec 2023 none Apache-2.0 — Details →
v7.0.1-0.20231115183548-d7ed7d5d91e6 15 Nov 2023 none Apache-2.0 — Details →
v7.0.1-0.20231101145709-3a12cbd29ca2 01 Nov 2023 none Apache-2.0 — Details →
v7.0.1-0.20231002115106-3835b6fd3b54 02 Oct 2023 none Apache-2.0 — Details →
v7.0.0 08 Sep 2023 none Apache-2.0 — Details →
v7.0.0-20230908133102-7a6111f0d21c 08 Sep 2023 none Apache-2.0 — Details →

All 41 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for github.com/checkpoint-restore/go-criu/v7

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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/checkpoint-restore/go-criu/v7

Is github.com/checkpoint-restore/go-criu/v7 safe to use?

Vulert has no vulnerabilities on record for github.com/checkpoint-restore/go-criu/v7 in Go at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is github.com/checkpoint-restore/go-criu/v7's Vulert package health score?

Vulert scores github.com/checkpoint-restore/go-criu/v7 62/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/checkpoint-restore/go-criu/v7 affected?

No. v7.2.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of github.com/checkpoint-restore/go-criu/v7 should I use?

v7.2.0 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/checkpoint-restore/go-criu/v7 have?

0 vulnerabilities are recorded for github.com/checkpoint-restore/go-criu/v7 in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/checkpoint-restore/go-criu/v7 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/checkpoint-restore/go-criu/v7 in the last 12 months. 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/checkpoint-restore/go-criu/v7 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/checkpoint-restore/go-criu/v7 for upcoming vulnerabilities?

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