VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

byteorder: vulnerability history, versions and safety

byteorder is a package in the crates.io ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the crates.io 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 byteorder vulnerabilities

Vulert verdict on byteorder 1.5.0 i

Updated on 23 Oct 2026

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

Package health score 68/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 1.5.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 20,051 packages i
  • Stars 1,101 i
  • OpenSSF scorecard 3/10 i
  • Last release 36 months ago i
  • Licence MIT OR Unlicense 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 byteorder, 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
1.5.0 06 Oct 2023 none MIT OR Unlicense — Details →
1.4.3 10 Mar 2021 none MIT OR Unlicense — Details →
1.4.2 08 Jan 2021 none MIT OR Unlicense — Details →
1.4.1 08 Jan 2021 none MIT OR Unlicense — Details →
1.4.0 08 Jan 2021 none MIT OR Unlicense — Details →
1.3.4 07 Feb 2020 none MIT OR Unlicense — Details →
1.3.3 07 Feb 2020 none MIT OR Unlicense — Details →
1.3.2 09 Jun 2019 none MIT OR Unlicense — Details →
1.3.1 22 Jan 2019 none MIT OR Unlicense — Details →
1.3.0 19 Jan 2019 none MIT OR Unlicense — Details →
1.2.7 26 Oct 2018 none MIT OR Unlicense — Details →
1.2.6 25 Aug 2018 none MIT OR Unlicense — Details →
1.2.5 25 Aug 2018 none MIT OR Unlicense — Details →
1.2.4 30 Jul 2018 none MIT OR Unlicense — Details →
1.2.3 12 May 2018 none MIT OR Unlicense — Details →
1.2.2 01 Apr 2018 none MIT OR Unlicense — Details →
1.2.1 29 Nov 2017 none MIT OR Unlicense — Details →
1.2.0 29 Nov 2017 none MIT OR Unlicense — Details →
1.1.0 09 Jul 2017 none MIT OR Unlicense — Details →
1.0.0 30 Dec 2016 none MIT OR Unlicense — Details →
0.5.3 01 Jun 2016 none MIT OR Unlicense — Details →
0.5.2 22 May 2016 none MIT OR Unlicense — Details →
0.5.1 24 Mar 2016 none MIT OR Unlicense — Details →
0.5.0 11 Mar 2016 none MIT OR Unlicense — Details →
0.4.2 07 Nov 2015 none MIT OR Unlicense — Details →
0.4.1 07 Nov 2015 none MIT OR Unlicense — Details →
0.4.0 07 Nov 2015 none MIT OR Unlicense — Details →
0.3.13 30 Aug 2015 none MIT OR Unlicense — Details →
0.3.12 30 Aug 2015 none MIT OR Unlicense — Details →
0.3.11 06 Jul 2015 none MIT OR Unlicense — Details →
0.3.10 20 May 2015 none MIT OR Unlicense — Details →
0.3.9 25 Apr 2015 none MIT OR Unlicense — Details →
0.3.8 22 Apr 2015 none MIT OR Unlicense — Details →
0.3.7 15 Apr 2015 none MIT OR Unlicense — Details →
0.3.6 15 Apr 2015 none MIT OR Unlicense — Details →
0.3.5 02 Apr 2015 none Unlicense — Details →
0.3.4 01 Apr 2015 none Unlicense — Details →
0.3.3 25 Mar 2015 none Unlicense — Details →
0.3.2 25 Mar 2015 none Unlicense — Details →
0.3.1 19 Mar 2015 none Unlicense — Details →
0.3.0 15 Mar 2015 none Unlicense — Details →
0.2.14 08 Mar 2015 none Unlicense — Details →
0.2.13 07 Mar 2015 none Unlicense — Details →
0.2.12 28 Feb 2015 none Unlicense — Details →
0.2.11 26 Feb 2015 none Unlicense — Details →
0.2.10 26 Feb 2015 none Unlicense — Details →
0.2.9 21 Feb 2015 none Unlicense — Details →
0.2.8 21 Feb 2015 none Unlicense — Details →
0.2.7 21 Feb 2015 none Unlicense — Details →
0.2.6 19 Feb 2015 none Unlicense — Details →
0.2.5 15 Feb 2015 none Unlicense — Details →
0.2.4 06 Feb 2015 none Unlicense — Details →
0.2.3 05 Feb 2015 none Unlicense — Details →
0.2.2 05 Feb 2015 none Unlicense — Details →
0.2.1 05 Feb 2015 none Unlicense — Details →
0.2.0 05 Feb 2015 none Unlicense — Details →
0.1.1 04 Feb 2015 none Unlicense — Details →
0.1.0 03 Feb 2015 none Unlicense — Details →

All 58 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 byteorder

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 byteorder

Is byteorder safe to use?

Vulert has no vulnerabilities on record for byteorder in crates.io 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 byteorder's Vulert package health score?

Vulert scores byteorder 68/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 byteorder affected?

No. 1.5.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 byteorder should I use?

1.5.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 byteorder have?

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

0 vulnerabilities were recorded for byteorder 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 byteorder 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 byteorder for upcoming vulnerabilities?

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