ZDF
Sign inSign up

Vulnerabilities

Vulnerability · RUSTSEC-2026-0500

BEEF validation answers valid for a raw entry that is not a transaction

Published Nov 10, 2026 · catalog updated Nov 12, 2026 · RustSec Rust

Last checked Nov 12, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for RUSTSEC-2026-0500. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.

Same product and reporting

Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
crates.io bsv-rs

and accept raw bytes without a . For bytes that are not exactly one transaction (a transaction followed by bytes, a cut transaction, bytes that are no transaction at all), , , and could answer valid, even with no BUMP and no parent in the BEEF, and, where the entry carried a BUMP index, treat the hash of those bytes as a proven transaction id; an entry that names it as a parent was answered valid too. The wire readers ( , , , ) parse every entry and are not affected. Reaching this needs an application that passes bytes it did not parse to or and then relies on the verdict or on the transaction the BEEF hands back. 0.8.5 refuses such an entry at all four verdict doors, with or without a BUMP index, and every entry that names it as a parent. Where upgrading is not possible, do not rely on or alone for such an entry: check that the bytes are exactly one transaction before merging them.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • crates.io bsv-rs0.0.0-0 → 0.8.5

How to fix RUSTSEC-2026-0500

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for RUSTSEC-2026-0500. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0.0.0-0 → 0.8.5. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Nov 10, 2026 · GitHub Advisory Database

    Detected

    and accept raw bytes without a . For bytes that are not exactly one transaction (a transaction followed by bytes, a cut transaction, bytes that are no transaction at all), , , and could answer valid, even with no BUMP and no parent in the BEEF, and, where the entry carried a BUMP index, treat the hash of those bytes as a proven transaction id; an entry that names it as a parent was answered valid

  2. Nov 12, 2026 · GitHub Advisory Database

    Fix available

    bsv-rs fixed in 0.8.5

  3. Nov 12, 2026 · GitHub Advisory Database

    Fix available

    bsv-rs fixed in 0.8.5

  4. Nov 12, 2026 · GitHub Advisory Database

    Updated

    and accept raw bytes without a . For bytes that are not exactly one transaction (a transaction followed by bytes, a cut transaction, bytes that are no transaction at all), , , and could answer valid, even with no BUMP and no parent in the BEEF, and, where the entry carried a BUMP index, treat the hash of those bytes as a proven transaction id; an entry that names it as a parent was answered valid

Sources

  • GitHub Advisory DatabasePackage advisoryGHSA-j8hr-pjhm-6h27

    GitHub Advisory Database record mirrored by OSV.

    github.com
  • OpenSSF OSV / OSV ScannerPackage advisoryRUSTSEC-2026-0500

    BEEF validation answers valid for a raw entry that is not a transaction

    osv.dev
  • RustSec Advisory DBVendor advisoryRUSTSEC-2026-0500

    and accept raw bytes without a . For bytes that are not exactly one transaction (a transaction followed by bytes, a cut transaction, bytes that are no transaction at all), , , and could answer valid, even with no BUMP and no parent in the BEEF, and, where the entry carried a BUMP

    crates.io

References

Freshness

Last verified in this catalog Nov 12, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • RustSec Advisory DBNov 12, 2026
  • GitHub Advisory DatabaseNov 12, 2026
  • OpenSSF OSV / OSV ScannerNov 12, 2026