Skip to main content
Public proof of conceptFix available

CVE-2020-26235

A public proof of concept exists; no exploitation attested.

  • Published2020-11-24
  • Fixed in0.2.23 · 0.2.6 · 0.2.5 · 0.2.4 · 0.2.3 · 0.2.2
  • WeaknessCWE-476

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2020-11-2422:15CVE publishedNVD
  2. 2026-11-0706:22First public proof of conceptPoC-in-GitHub

Versions per branch

NVD · OSV
Time project timeversion to verify
BranchAffectedFixed in
0.2≥ 0.2.7, < 0.2.230.2.23
0.x≥ 0.1.0, < 0.2.230.2.23
0.2≥ 0.2.7-0, < 0.2.230.2.23
0.2≥ 0.2.6-0, < 0.2.60.2.6
0.2≥ 0.2.5-0, < 0.2.50.2.5
0.2≥ 0.2.4-0, < 0.2.40.2.4
0.2≥ 0.2.3-0, < 0.2.30.2.3
0.2≥ 0.2.2-0, < 0.2.20.2.2
0.2≥ 0.2.1-0, < 0.2.10.2.1
0.x≥ 0.0.0-0, < 0.2.00.2.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • bergWolfiall versions · fixed in 0.4.7-r0
  • bergChainguardall versions · fixed in 0.4.7-r0
  • newsboatCleanStartall versions · fixed in 2.30.1-r0
  • newsboatAlpine:v3.24all versions · fixed in 2.30.1-r0
  • newsboatAlpine:v3.23all versions · fixed in 2.30.1-r0
  • newsboatAlpine:v3.22all versions · fixed in 2.30.1-r0
  • newsboatAlpine:v3.21all versions · fixed in 2.30.1-r0
  • newsboatAlpine:v3.20all versions · fixed in 2.30.1-r0

16 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update Time project time to 0.2.23 · 0.2.6 · 0.2.5 · 0.2.4 · 0.2.3 · 0.2.2 · 0.2.1 · 0.2.0

Advisories and patches

Detection

read 2026-11-07 06:22 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CNACVSS 3.15.3known since 2026-10-23
  • NVDCVSS 3.15.3read 2026-10-23
  • NVDCVSS 2.03.5read 2026-10-23
  • CNAweakness (CWE)CWE-476known since 2026-10-23
  • NVDweakness (CWE)CWE-476read 2026-10-23
  • FIRST EPSSEPSS score2.0 %2026-11-08
  • PoC-in-GitHubproof of concept1known since 2026-11-07
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryMODERATE2021-08-18

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Published
2020-11-24
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-wcg3-cvx6-7396

Frequently asked questions

What is CVE-2020-26235?

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.

Is CVE-2020-26235 actively exploited?

Active exploitation of CVE-2020-26235 has not been confirmed. Its EPSS score was 2.0% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-26235?

CVE-2020-26235 has a CVSS v3 base score of 5.3 (MEDIUM severity), with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H.

Running time? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record