<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 21:12:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-25727 — time affected by a stack exhaustion denial of service attack</title>
      <link>https://db.gcve.eu/vuln/cve-2026-25727</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; time-rs time&lt;/p&gt;
&lt;p&gt;time provides date and time handling in Rust. From 0.3.6 to before 0.3.47, 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. 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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; time-rs time&lt;/p&gt;
&lt;p&gt;time provides date and time handling in Rust. From 0.3.6 to before 0.3.47, 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. 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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-25727</guid>
    </item>
    <item>
      <title>GHSA-r6v5-fh4h-64xc — time vulnerable to stack exhaustion Denial of Service attack</title>
      <link>https://db.gcve.eu/vuln/ghsa-r6v5-fh4h-64xc</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: time&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Alternatively, avoiding the format altogether would also ensure that the vulnerability is not encountered. To do this, add&lt;/p&gt;
&lt;p&gt;```toml
disallowed-types = [&amp;#34;time::format_description::well_known::Rfc2822&amp;#34;]
```&lt;/p&gt;
&lt;p&gt;to your `clippy.toml` file. This will trigger the `clippy::disallowed_types` lint, which is warn-by-default and can be explicitly denied.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: time&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Alternatively, avoiding the format altogether would also ensure that the vulnerability is not encountered. To do this, add&lt;/p&gt;
&lt;p&gt;```toml
disallowed-types = [&amp;#34;time::format_description::well_known::Rfc2822&amp;#34;]
```&lt;/p&gt;
&lt;p&gt;to your `clippy.toml` file. This will trigger the `clippy::disallowed_types` lint, which is warn-by-default and can be explicitly denied.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-r6v5-fh4h-64xc</guid>
    </item>
  </channel>
</rss>
