Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

time

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.8crates.ioPublished

    time vulnerable to stack exhaustion Denial of Service attack

    CVE-2026-25727 · GHSA-r6v5-fh4h-64xc

    Affected
    • crates.io time >= 0.3.6, < 0.3.47
    Fixed in
    0.3.47· Vendor fix available
    Issue
    Impact When user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprecated and rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary, non-malicious input will never encounter this scenario. Patches A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned rather than exhausting the stack. Workarounds Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of the stack consumed would be at most a factor of the length of the input. Alternatively, avoiding the format altogether would also ensure that the vulnerability is not encountered. To do this, add to your clippy.toml file. This will trigger the clippy::disallowedtypes lint, which is warn-by-default and can be explicitly denied.

    Recommended action: Upgrade to 0.3.47 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →