https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-05T19:47:37.938586+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-45998 EUVD-2026-45998 2026-10-05T19:47:37.944876+00:00 EUVD-2026-45998 https://cve.radiocsirt.org/vuln/fkie_cve-2020-26235 fkie_cve-2020-26235 2026-10-05T19:47:37.944927+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-wcg3-cvx6-7396 GHSA-wcg3-cvx6-7396 — Segmentation fault in time 2026-10-05T19:47:37.944980+00:00

Affected: crates.io: time

### Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

The affected functions from time 0.2.7 through 0.2.22 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` - `time::OffsetDateTime::try_now_local`

The affected functions in time 0.1 (all versions) are:

- `at` - `at_utc` - `now`

Non-Unix targets (including Windows and wasm) are unaffected.

### Patches

In some versions of `time`, the internal method that determines the local offset has been modified to always return `None` on the affected operating systems. This has the effect of returning an `Err` on the `try_*` methods and `UTC` on the non-`try_*` methods. In later versions, `time` will attempt to determine the number of threads running in the process. If the process is single-threaded, the call will proceed as its safety invariant is upheld.

Users and library authors with time in their dependency tree must perform `cargo update`, which will pull in the updated, unaffected code.

Users of time 0.1 do not have a patch and must upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.

### Workarounds

Libra…

 https://cve.radiocsirt.org/vuln/gsd-2020-26235 gsd-2020-26235 2026-10-05T19:47:37.945059+00:00 gsd-2020-26235 https://cve.radiocsirt.org/vuln/opensuse-su-2024:12746-1 openSUSE-SU-2024:12746-1 — newsboat-2.30.1-1.1 on GA media 2026-10-05T19:47:37.945084+00:00

newsboat-2.30.1-1.1 on GA media

 https://cve.radiocsirt.org/vuln/rustsec-2020-0071 RUSTSEC-2020-0071 — Potential segfault in the time crate 2026-10-05T19:47:37.945121+00:00

Affected: crates.io: time

### Impact

The affected functions set environment variables without synchronization. On Unix-like operating systems, this can crash in multithreaded programs. Programs may segfault due to dereferencing a dangling pointer if an environment variable is read in a different thread than the affected functions. This may occur without the user's knowledge, notably in the Rust standard library or third-party libraries.

The affected functions from time 0.2.7 through 0.2.22 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` - `time::OffsetDateTime::try_now_local`

The affected functions in time 0.1 (all versions) are:

- `time::at_utc` - `time::at` - `time::now` - `time::tzset`

Non-Unix targets (including Windows and wasm) are unaffected.

### Patches

Pending a proper fix, the internal method that determines the local offset has been modified to always return `None` on the affected operating systems. This has the effect of returning an `Err` on the `try_*` methods and `UTC` on the non-`try_*` methods.

Users and library authors with time in their dependency tree should perform `cargo update`, which will pull in the updated, unaffected code.

Users of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.

### Workarounds

A possible workaround for crates affected thr…

 https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-26235 UBUNTU-CVE-2020-26235 2026-10-05T19:47:37.945222+00:00

Affected: Ubuntu:20.04:LTS: rust-time, Ubuntu:22.04:LTS: rust-time, Ubuntu:24.04:LTS: rust-time, Ubuntu:25.10: rust-time, Ubuntu:26.04:LTS: rust-time

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.