Vulnerability Database · crates.io · bytes · Version
bytes 1.3.0
1.3.0 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.12.1.
Critical 0 High 0 Medium 1 Low 0 Unrated 1
-
Released 21 Nov 2022
Licence MIT
Also known from other sources 2
Newer releases 59
Database updated 23/Oct/2026
Release and licence data published by crates.io. 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 Vulnerabilities affecting this version
bytes 1.3.0 vulnerabilities
2 vulnerabilities cover bytes 1.3.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Integer Overflow Vulnerability in Bytes Package: BytesMut::reserve | 5.4 medium | 1.11.1 | 03 Feb 2026 |
| Integer Overflow Vulnerability in Bytes Package: A Risk to Memory Safety | N/A unrated | 1.11.1 | 03 Feb 2026 |
Looking for another version, or everything Vulert holds for bytes?
Questions
About bytes 1.3.0
Is bytes 1.3.0 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover bytes 1.3.0: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. The upgrade Vulert recommends is 1.12.1, and each entry above names the fixed version to move to.
Which version of bytes should I use instead of 1.3.0?
1.12.1 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 1.3.0 the latest release of bytes?
No. 1.3.0 was published 21 Nov 2022, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor bytes for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the bytes version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.