Security: 3 vulnerabilities found

[github-actions]

Security Audit Report

Date: 2026-02-06T04:18:44.079Z
Vulnerabilities: 3

RUSTSEC-2026-0007: Integer overflow in BytesMut::reserve

Package: bytes@1.11.0
Severity: Unknown
URL: GHSA-434x-w66g-qw3r

In the unique reclaim path of BytesMut::reserve, the condition

if v_capacity >= new_cap + offset

uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB.

This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.

PoC

use bytes::*;

fn main() {
    let mut a = BytesMut::from(&b"hello world"[..]);
    let mut b = a.split_off(5);

    // Ensure b becomes the unique owner of the backing storage
    drop(a);

    // Trigger overflow in new_cap + offset inside reserve
    b.reserve(usize::MAX - 6);

    // This call relies on the corrupted cap and may cause UB & HBO
    b.put_u8(b'h');
}

Workarounds

Users of BytesMut::reserve are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply.

Patched Versions: >=1.11.1

---

RUSTSEC-2023-0071: Marvin Attack: potential key recovery through timing sidechannels

Package: rsa@0.9.10
Severity: Unknown
URL: RustCrypto/RSA#19 (comment)

Impact

Due to a non-constant-time implementation, information about the private key is leaked through timing information which is observable over the network. An attacker may be able to use that information to recover the key.

Patches

No patch is yet available, however work is underway to migrate to a fully constant-time implementation.

Workarounds

The only currently available workaround is to avoid using the rsa crate in settings where attackers are able to observe timing information, e.g. local use on a non-compromised computer is fine.

References

This vulnerability was discovered as part of the "Marvin Attack", which revealed several implementations of RSA including OpenSSL had not properly mitigated timing sidechannel attacks.

Patched Versions: None

---

RUSTSEC-2025-0111: tokio-tar parses PAX extended headers incorrectly, allows file smuggling

Package: tokio-tar@0.3.1
Severity: Unknown
URL: https://edera.dev/stories/tarmageddon

The archive reader incorrectly handles PAX extended headers, when the ustar
header incorrectly specifies zero size (size=000000000000), while a PAX
header specifies a non-zero size, tokio-tar::Archive is going to read the
file content as tar entry header.

This can be used by a tar file to present different content to tokio-tar
compared to other tar reader implementations.

This bug is also known as CVE-2025-62518 and GHSA-j5gw-2vrg-8fgx, as those
crates share a common ancestor codebase.

The tokio-tar crate is archived and no longer maintained, we recommend you
switch to an alternative crate such as:

• astral-tokio-tar

Patched Versions: None

---

This issue was automatically created by the security audit workflow.