VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

pnet_packet: vulnerability history, versions and safety

pnet_packet is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 8 releases, from Jun 2020 to Feb 2023. 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.

See all pnet_packet vulnerabilities

Vulert verdict on pnet_packet 0.35.0 i

Updated on 23 Oct 2026

Good news: 0.35.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

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

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

  • Current release 0.35.0 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 0 in the last year i
  • Latest disclosure 09 Feb 2023 i
  • Highest CVSS 6.0 i
  • With no published fix 0 i
  • Stars 2,592 i
  • OpenSSF scorecard 3/10 i
  • Last release 28 months ago i
  • Licence Apache-2.0 OR MIT i

Version list, release dates, licence and dependants published by crates.io, 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 pnet_packet, 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
0.35.0 30 May 2024 none Apache-2.0 OR MIT — Details →
0.34.0 19 Jul 2023 none Apache-2.0 OR MIT — Details →
0.33.0 03 Feb 2023 none Apache-2.0 OR MIT — Details →
0.32.0 03 Feb 2023 none Apache-2.0 OR MIT — Details →
0.31.0 01 Jun 2022 none Apache-2.0 OR MIT — Details →
0.30.0 12 May 2022 none Apache-2.0 OR MIT — Details →
0.29.0 13 Jan 2022 none Apache-2.0 OR MIT — Details →
0.28.0 15 May 2021 none Apache-2.0 OR MIT — Details →
0.27.2 27 Nov 2020 none Apache-2.0 OR MIT — Details →
0.27.1 27 Nov 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.26.0 01 May 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.23.1 08 Jan 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.25.0 08 Jan 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.23.0 06 Nov 2019 M1 U1 Apache-2.0 OR MIT Yes Details →
0.22.0 21 Feb 2019 M1 U1 Apache-2.0 OR MIT Yes Details →
0.21.0 07 Mar 2018 M1 U1 Apache-2.0 OR MIT Yes Details →
0.20.0 30 Oct 2017 M1 U1 Apache-2.0 OR MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2023 1

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 pnet_packet

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-0167: Buffer overrun in pnet_packet set_payload setters 6.0 medium 0.27.2 19 Jun 2020
Buffer Overrun Vulnerability in pnet_packet 6.0 medium 0.27.2 09 Feb 2023

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 pnet_packet

Is pnet_packet safe to use?

Vulert records 2 vulnerabilities for pnet_packet in crates.io: 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 pnet_packet's Vulert package health score?

Vulert scores pnet_packet 67/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 pnet_packet affected?

No. 0.35.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 pnet_packet should I use?

0.35.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 pnet_packet have?

2 vulnerabilities are recorded for pnet_packet in the crates.io 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 pnet_packet vulnerabilities disclosed?

0 vulnerabilities were recorded for pnet_packet in the last 12 months, and the oldest entry in this database dates to 19 Jun 2020. 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 pnet_packet 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 pnet_packet for upcoming vulnerabilities?

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