Comparison Overview
City of Riverside

City of Riverside
US
Last Update: 02/04/2026
The rapidly growing City of Riverside currently ranks as the 12th largest city in California, 6th in Southern California, and is the largest city in one of the fastest growing regions in the United States. It is home to four internationally recognized universities and ...

NOAA: National Oceanic & Atmospheric Administration
1401 Constitution Avenue NW, Washington, 20230, US
Last Update: 04/04/2026
Welcome! We're the National Oceanic & Atmospheric Administration or NOAA. From daily weather forecasts, severe storm warnings and climate monitoring to fisheries management, coastal restoration and supporting marine commerce, our products and services support economic ...
Compliance Ranges Comparison

City of Riverside







NOAA: National Oceanic & Atmospheric Administration






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for City of Riverside in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for NOAA: National Oceanic & Atmospheric Administration in 2026.
Incident History - City of Riverside (X = Date, Y = Severity)
City of Riverside cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NOAA: National Oceanic & Atmospheric Administration (X = Date, Y = Severity)
NOAA: National Oceanic & Atmospheric Administration cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

City of Riverside

NOAA: National Oceanic & Atmospheric Administration
FAQ
Latest Global CVEs
Deserialization of untrusted data in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.
The Bluetooth BAP Broadcast Assistant GATT client in subsys/bluetooth/audio/bap_broadcast_assistant.c reassembled remote Broadcast Receive State data into a single file-static net_buf_simple (att_buf, BT_ATT_MAX_ATTRIBUTE_LEN = 512 bytes) shared by all connection instances, while the BUSY flag, long-read handle, and reset/offset state were per-connection. When the device acts as a Broadcast Assistant connected to multiple Scan Delegator peripherals, notification and long-read callbacks from different connections interleave on the shared buffer: the append in notify_handler (net_buf_simple_add_mem at the not-busy branch) performs no tailroom check, so receive-state notifications from two or more delegators accumulate on the same 512-byte buffer and, with a sufficiently large configured ATT MTU (BT_L2CAP_TX_MTU up to 2000) and two-to-three concurrent connections, write past the buffer into adjacent .bss (net_buf_simple_add only asserts in debug builds). Even below the overflow threshold, one connection's net_buf_simple_reset zeroes the shared length while another connection's reassembly and GATT read offset are in flight, mixing one peer's data into another's parse. A malicious or compromised Scan Delegator (or two colluding peers) over BLE can trigger this, causing out-of-bounds writes (memory corruption / denial of service) and cross-connection data corruption. The fix moves the buffer into the per-connection instance struct so each connection reassembles into its own buffer. Affects Zephyr releases shipping the Broadcast Assistant with the shared buffer, including v4.4.0 and earlier.
ImageMagick before 7.1.2-26 contains a memory leak vulnerability in the VIFF encoder when memory allocation fails. Attackers can trigger allocation failures by processing specially crafted VIFF images to exhaust available memory and cause denial of service.
ImageMagick before 7.1.2-26 contains a use-after-free vulnerability in the FormatMagickCaption method when memory allocation fails. Attackers can trigger memory allocation failures to cause a dangling pointer to reference freed memory, potentially enabling denial of service or code execution.
ImageMagick before 7.1.2-26 contains a policy bypass vulnerability in the APNG encoder and external delegates due to missing validation checks. Attackers can write files to disallowed paths by bypassing configured policy restrictions through the APNG encoding process.