ZDF
Sign inSign up

Vulnerabilities

Vulnerability · RUSTSEC-2026-0501

Shamir backup recovery accepts a share at x = 0, so a supplied share can substitute the recovered private key

Published 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-0501. 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

(the Shamir backup share reader, public since 0.2.0, the crate's first release) accepted a share whose x coordinate is 0, and interpolates the shares at x = 0 to recover the key. At an x of 0 the interpolation answers that share's y value alone, so an attacker who supplies one share in that form — with the share's integrity tag ground to match the honest set's — chooses the recovered key outright. The non-canonical zero x = p works the same way, and a repeated x past the threshold window also passed. An application that recovers a Shamir backup from shares it did not produce — a custodian's me

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

How to fix RUSTSEC-2026-0501

  • 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-0501. 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 12, 2026 · RustSec Advisory DB

    Detected

    (the Shamir backup share reader, public since 0.2.0, the crate's first release) accepted a share whose x coordinate is 0, and interpolates the shares at x = 0 to recover the key. At an x of 0 the interpolation answers that share's y value alone, so an attacker who supplies one share in that form — with the share's integrity tag ground to match the honest set's — chooses the recovered key outright.

Sources

  • RustSec Advisory DBVendor advisoryRUSTSEC-2026-0501

    (the Shamir backup share reader, public since 0.2.0, the crate's first release) accepted a share whose x coordinate is 0, and interpolates the shares at x = 0 to recover the key. At an x of 0 the interpolation answers that share's y value alone, so an attacker who supplies one sh

    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