ZDF
Sign inSign up

Vulnerabilities

Vulnerability · RUSTSEC-2026-0497

Transaction::from_json holds an input txid that is not 64 hex digits and writes the input as spending the zero txid

Published Nov 11, 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-0497. 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 version range is stored. A customer cannot check an installed version against 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
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Not established
Affected products
RustSec Rust

, for a document with no member, held each input's member as given. An input that is not 64 hex digits ( , , 63 or 65 digits, characters that are not hex digits) answered : and gave the text back, while wrote the input as spending the txid of 32 zero bytes and hashed those bytes. Documents naming different texts were one transaction, spending an outpoint none of them named. An application that reads a peer's transaction document with and relies both on the text of its inputs and on its bytes or is affected; one that reads only documents it produced is not. 0.8.6 refuses such a txid ( ). Where

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix RUSTSEC-2026-0497

  • No stored fix

    No vendor fix text is stored. Use the linked advisory before you change production.

  • Version check

    No version range is stored, so an installed version cannot be checked on this page.

  • Advisory

    Open the rustsec record and follow its fix.

  • Official advisories

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-0497. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Which versions are affected?

Affected version ranges are not on this record. 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.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Nov 11, 2026 · RustSec Advisory DB

    Detected

    , for a document with no member, held each input's member as given. An input that is not 64 hex digits ( , , 63 or 65 digits, characters that are not hex digits) answered : and gave the text back, while wrote the input as spending the txid of 32 zero bytes and hashed those bytes. Documents naming different texts were one transaction, spending an outpoint none of them named. An application that rea

Sources

  • RustSec Advisory DBVendor advisoryRUSTSEC-2026-0497

    , for a document with no member, held each input's member as given. An input that is not 64 hex digits ( , , 63 or 65 digits, characters that are not hex digits) answered : and gave the text back, while wrote the input as spending the txid of 32 zero bytes and hashed those bytes.

    crates.io

Freshness

Last verified in this catalog Unknown date. 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