Skip to main content
VulnerabilityPublished Updated

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

Affects bsv-rsSource GCVE Database

0

CVSS 5.3 Medium : upgrade to 0.9.0-beta.7.0 or 0.8.5 when convenient.

Data as of 12 Nov 2026, 08:07 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 0.9.0-beta.7.0, 0.8.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

What to do

Upgrade bsv-rs to 0.9.0-beta.7.0 or 0.8.5.

Affected software

ProductAffectedFixed in
crates.iobsv-rspkg:cargo/bsv-rsOther threatsAffected
  • >=0.0.0-0 <0.8.5
  • >=0.9.0-beta.1 <0.9.0-beta.7.0
Fixed in
  • 0.8.5
  • 0.9.0-beta.7.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to bsv-rs version 0.8.5 or later, or 0.9.0-beta.7.0 or later, where trailing bytes after a transaction are rejected. If upgrading is not possible, parse transactions with Transaction::from_binary, call tx.invalidate_caches(), and verify that tx.to_binary() exactly matches the input bytes to ensure no trailing data is present.

Description

The bsv-rs library versions before 0.8.5 and certain beta versions allow transaction readers to accept trailing bytes after a parsed transaction. This causes the transaction's cached serialization and ID to include extra bytes, potentially resulting in a transaction being identified by a different ID than expected. The issue is fixed in versions 0.8.5 and 0.9.0-beta.7.0.

References

Community reviews

Loading reviews…