time-rs time up to 0.3.46 stack-based overflow

Summaryinfo

A vulnerability was found in time-rs time up to 0.3.46. It has been rated as critical. Affected by this vulnerability is an unknown functionality. The manipulation leads to stack-based overflow. This vulnerability is traded as CVE-2026-25727. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in time-rs time up to 0.3.46. This issue affects an unknown function. The manipulation with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). Impacted is availability. The summary by CVE is:

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.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-25727 since 02/05/2026. The exploitation is known to be difficult. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 298198 (Linux Distros Unpatched Vulnerability : CVE-2026-25727), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 0.3.47 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 1c63dc7985b8fa26bd8c689423cc56b7a03841ee is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (298198) and EUVD (EUVD-2026-5587). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• time-rs

Name

• time

Version

• 0.3.0
• 0.3.1
• 0.3.2
• 0.3.3
• 0.3.4
• 0.3.5
• 0.3.6
• 0.3.7
• 0.3.8
• 0.3.9
• 0.3.10
• 0.3.11
• 0.3.12
• 0.3.13
• 0.3.14
• 0.3.15
• 0.3.16
• 0.3.17
• 0.3.18
• 0.3.19
• 0.3.20
• 0.3.21
• 0.3.22
• 0.3.23
• 0.3.24
• 0.3.25
• 0.3.26
• 0.3.27
• 0.3.28
• 0.3.29
• 0.3.30
• 0.3.31
• 0.3.32
• 0.3.33
• 0.3.34
• 0.3.35
• 0.3.36
• 0.3.37
• 0.3.38
• 0.3.39
• 0.3.40
• 0.3.41
• 0.3.42
• 0.3.43
• 0.3.44
• 0.3.45
• 0.3.46

License

• open-source

Website

• Product: https://github.com/time-rs/time/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion