Advisory

RUSTSEC-2026-0498

Also known as: GHSA-j8hr-pjhm-6h27, RUSTSEC-2026-0500

Summary

Transaction readers accept trailing bytes, so a parsed transaction can carry another transaction id

Details

Transaction::from_binary and Transaction::from_hex read one transaction
from the front of their input, did not check that the input ended there, and
kept the whole input as the transaction's cached serialization: to_binary,
to_hex and id() then answered for bytes that are not the transaction's.
Transaction::from_json, given a hex field, reads it through from_hex and
answers the same. from_ef, from_hex_ef and parse_script_offsets also
read a prefix.

An application that takes bytes or hex from outside, parses them with these
readers and then uses id() or the serialization could be given one
transaction under another identity: the same parsed fields, a different id.
An application that passes them only bytes it produced or has already checked
is not affected.

0.8.5 refuses a byte after the transaction; Transaction::from_reader reads
from the front of a longer buffer. Where upgrading is not possible, parse with
Transaction::from_binary, call tx.invalidate_caches() (public from 0.3.16)
and require tx.to_binary() == bytes.

Severity

Medium Basis: CVSS v3 score 5.3, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Dates

Published
2026-11-10 12:00 UTC
Modified
2026-11-12 08:11 UTC

Affected packages and fixes

bsv-rs

crates.io · All systems

Affected

  • introduced 0.0.0-0, fixed 0.8.5, introduced 0.9.0-beta.1, fixed 0.9.0-beta.7.0 (semver)

Fixed versions

0.8.5, 0.9.0-beta.7.0

Fix

  • Fixed version 0.8.5
    cargo update -p bsv-rs --precise 0.8.5
  • Fixed version 0.9.0-beta.7.0
    cargo update -p bsv-rs --precise 0.9.0-beta.7.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences