CVE Watch379,124 in full archive

Vulnerabilities exploitable today

379,124in current view

Single score combining CVSS, KEV membership and EPSS. Every CVE with its own record — timeline from publication to active exploitation.

In KEV catalog1,721

New KEV · 24H0

Exploit Today ≥ 701,654

Distribution · last window

Critical
2,385
High
8,589
Medium
7,035
Low
793

Filters

Window

Severity

Flags

Vulnerabilities378,961–379,000 · 379,124

CVECVSSEPSSKEVRExploitTitleMod.

CVE-2026-26348—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.44d CVE-2023-41087—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27d CVE-2026-69099—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.33d CVE-2026-158905.3 MED

0.0%

——0The default AEAD nonce provider for the PSA Internal Trusted Storage transform module, secure_storage_its_transform_aead_get_nonce() in subsys/secure_storage/src/its/transform/aead_get.c, stores its nonce counter in unsynchronized function-local static variables (s_nonce and s_nonce_initialized). Every ITS write obtains its AES-GCM or ChaCha20-Poly1305 nonce here via secure_storage_its_transform_to_store(). Because the function held no lock, two threads calling it concurrently race on the shared statics: the initialization path (psa_generate_random() followed by memcpy()) and the non-atomic increment-then-copy path can each hand the same nonce value to two distinct encryption operations, and can lose increments so the counter repeats values it was designed never to repeat. The ITS layer (secure_storage_its_set() in subsys/secure_storage/src/its/implementation.c) performs no serialization of its own, so concurrent same-UID writes reach the racy provider directly. Reusing a nonce with the same key under AES-GCM or ChaCha20-Poly1305 is a catastrophic AEAD failure: it leaks the XOR of the two plaintexts (ITS routinely stores secrets, including PSA persistent keys) and, for GCM, exposes the authentication key, enabling forgery of stored entries. Because the AEAD key is derived per entry UID, the security-relevant collision is two concurrent writes to the same UID both receiving the same nonce; an adversary able to read the raw backing storage can then exploit the reuse. Both ITS store back-ends shipped with Zephyr, zms.c and the settings/NVS back-end in settings.c, are log-structured flash stores with deferred garbage collection, so an entry superseded by a rewrite remains physically present in the partition until its sector is reclaimed. Two same-UID writes that race therefore leave both ciphertexts readable in the raw image at once, which is the condition the nonce reuse needs to be exploitable. The trigger remains narrow: both built-in key providers (DEVICE_ID_HASH and ENTRY_UID_HASH) salt the derived key with the entry UID, so reuse across different UIDs is harmless, and the exposure requires an application that writes the same UID concurrently from two threads. The fix serializes the provider with a K_MUTEX_DEFINE(s_nonce_mutex) held for the duration of nonce generation.1d CVE-2026-53991—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.33d CVE-2022-51006—

—

——0Rejected reason: This CVE ID has been rejected.27d CVE-2026-18745—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.19d CVE-2026-8717—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.34d CVE-2026-51255—

—

——0Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.54d CVE-2026-51240—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.33d CVE-2025-66333—

0.0%

——0——CVE-2026-25549—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.44d CVE-2026-62169—

—

——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2026-61430. Reason: This candidate is a duplicate of CVE-2026-61430. Notes: All CVE users should reference CVE-2026-61430 instead of this candidate.70d CVE-2026-72905—

—

——0Rejected reason: Further research determined the issue is not a vulnerability.44d CVE-2026-5480—

—

——0Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage.22d CVE-2026-34423—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.44d CVE-2026-22656—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.44d CVE-2023-7354—

—

——0Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned.49d CVE-2023-54388—

—

——0Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned.49d CVE-2023-35771—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27d CVE-2026-15926—

—

——0Rejected reason: Red Hat Product Security has determined that this CVE ID is not needed20d CVE-2026-73111—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.36d CVE-2026-23675—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.44d CVE-2026-54385—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.37d CVE-2023-45214—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27d CVE-2023-54384—

—

——0Rejected reason: Erroneously reserved under wrong year by automation defect; never assigned.49d CVE-2023-31270—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27d CVE-2023-27381—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27d CVE-2026-86477—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.44d CVE-2026-57835—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.33d CVE-2023-54376—

—

——0Rejected reason: Erroneously reserved under wrong year by automation defect; superseded by correct-year CVE.49d CVE-2026-73188—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Duplicate to CVE-2026-13610.41d CVE-2023-30761—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused27d CVE-2026-51386—

—

——0Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2026-46409. Reason: This record is a reservation duplicate of CVE-2026-46409. Notes: All CVE users should reference CVE-2026-46409 instead of this record. All references and descriptions in this record have been removed to prevent accidental usage.65d CVE-2026-51276—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.40d CVE-2023-22433—

—

——0Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused28d