Skip to content
Fencer Vulns
medium 5.3

CVE-2020-26235 json

Segmentation fault in Rust time crate

published 2020-11-18 5 y ago modified 2026-09-10 1 mo ago also GHSA-wcg3-cvx6-7396 , RUSTSEC-2020-0071 , EUVD-2021-1914

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

In Rust time crate from version 0.2.7 and before version 0.2.23, unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires the user to set any environment variable in a different thread than the affected functions. The affected functions are time::UtcOffset::local_offset_at, time::UtcOffset::try_local_offset_at, time::UtcOffset::current_local_offset, time::UtcOffset::try_current_local_offset, time::OffsetDateTime::now_local and time::OffsetDateTime::try_now_local. Non-Unix targets are unaffected. This includes Windows and wasm. The issue was introduced in version 0.2.7 and fixed in version 0.2.23.

Patch / fix

  • crates.io time 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.2.4, 0.2.5, 0.2.6, 0.2.23
  • time_project time 0.2.23
  • newsboat Alpine 3.24, Alpine 3.23, Alpine 3.22 +5 more 2.30.1-r0

alpine advisories ALPINE-CVE-2020-26235

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-26235 updated cvss 5.3

rust-time: potential segmentation fault due to dangling pointer dereference

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.97% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:N/I:N/A:P
GitHub 3.1 6.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 6.2 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
crates.io time
>=0.1.0, <0.2.23
>=0.2.7, <0.2.23
>=0.0.0-0, <0.2.0
>=0.2.1-0, <0.2.1
>=0.2.2-0, <0.2.2
>=0.2.3-0, <0.2.3
>=0.2.4-0, <0.2.4
>=0.2.5-0, <0.2.5
>=0.2.6-0, <0.2.6
>=0.2.7-0, <0.2.23
0.2.23
0.2.0
0.2.1
0.2.2
0.2.3
0.2.4
0.2.5
0.2.6

Affected products

  • time-rs time

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.