Security incident · RUSTSEC-2026-0334
BIP-322 address ownership verification bypass for P2WPKH and P2SH-P2WPKH addresses
Published Aug 14, 2026 · RustSec Rust
Open the advisory
Exploitation likelihood is not on this record for RUSTSEC-2026-0334. 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.
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Awaiting synchronization with FIRST
- Remediation
- Not established
- Affected products
- RustSec Rust
Affected versions of accepted a BIP-322 proof created with an attacker-controlled private key as a valid signature for an unrelated victim P2WPKH or P2SH-P2WPKH address, allowing complete authentication bypass in applications using , , , or as proof that a user controls a Bitcoin address. In , the verifier obtained the public key from the caller-controlled witness and passed it to , where the supposed public-key mismatch check read the key from the same witness and compared it with itself: Since was originally parsed from that exact witness element, this comparison was tautological. The code v
No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.
How to fix RUSTSEC-2026-0334
Recommended remediation
No required-action text, fix commit, or clear fixed-version range is stored yet.
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-0334. 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.
Aug 14, 2026 · RustSec Advisory DB
Detected
Affected versions of accepted a BIP-322 proof created with an attacker-controlled private key as a valid signature for an unrelated victim P2WPKH or P2SH-P2WPKH address, allowing complete authentication bypass in applications using , , , or as proof that a user controls a Bitcoin address. In , the verifier obtained the public key from the caller-controlled witness and passed it to , where the supp
Sources
- RustSec Advisory DBVendor advisoryRUSTSEC-2026-0334
Affected versions of accepted a BIP-322 proof created with an attacker-controlled private key as a valid signature for an unrelated victim P2WPKH or P2SH-P2WPKH address, allowing complete authentication bypass in applications using , , , or as proof that a user controls a Bitcoin
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.