ZDF
Sign inSign up

Vulnerabilities

Vulnerability · RUSTSEC-2026-0431

Unbounded memory allocation in parsing a file

Published Nov 1, 2026 · RustSec Rust

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

Open the advisory

Exploitation likelihood is not on this record for RUSTSEC-2026-0431. 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

Affected versions of did not bound a per-entry payload length read from a file before allocating a buffer sized from it, allowing a tiny crafted file to force a multi-gigabyte allocation and abort the process (out-of-memory denial of service, CWE-400). ## Details In ( ), the per-entry payload length is read as a straight from the file and used to size a zeroing buffer **before** any data is read: The only check on is that it fits in ; there is no check that it fits within the bytes remaining in the file. An entry header declaring a ~4 GiB length therefore makes the crate request a ~4 GiB alloc

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

How to fix RUSTSEC-2026-0431

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

    Detected

    Affected versions of did not bound a per-entry payload length read from a file before allocating a buffer sized from it, allowing a tiny crafted file to force a multi-gigabyte allocation and abort the process (out-of-memory denial of service, CWE-400). ## Details In ( ), the per-entry payload length is read as a straight from the file and used to size a zeroing buffer **before** any data is read:

Sources

  • RustSec Advisory DBVendor advisoryRUSTSEC-2026-0431

    Affected versions of did not bound a per-entry payload length read from a file before allocating a buffer sized from it, allowing a tiny crafted file to force a multi-gigabyte allocation and abort the process (out-of-memory denial of service, CWE-400). ## Details In ( ), the per-

    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 7, 2026