Comparison Overview
State of Arizona

State of Arizona
1700 W Washington St, Phoenix, 85007, US
Last Update: 10/04/2026
As public servants, we deeply care about Arizona and are committed to facing the issues of our state head-on. We share a perseverance and dedication to ensuring a better future for every family and community in Arizona. We provide outstanding service to residents and or...

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

State of Arizona







NOAA: National Oceanic & Atmospheric Administration






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
State of Arizona has 30.56% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for NOAA: National Oceanic & Atmospheric Administration in 2026.
Incident History - State of Arizona (X = Date, Y = Severity)
State of Arizona 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

State of Arizona

NOAA: National Oceanic & Atmospheric Administration
FAQ
Latest Global CVEs
A flaw was found in libsoup. After a CONNECT tunnel is established through an HTTP proxy, libsoup incorrectly attaches the Proxy-Authorization header to subsequent HTTPS requests sent through that tunnel to the destination server. This allows the destination server to capture proxy credentials, leading to information disclosure.
A flaw was found in libsoup. The chunked transfer encoding parser uses a permissive parsing function for chunk sizes that silently accepts inputs violating RFC 9112, including leading whitespace, plus sign prefixes, and trailing invalid characters. When libsoup operates behind a strict frontend proxy, this parsing differential can be exploited to smuggle HTTP requests.
A flaw was found in libsoup. An unsigned integer underflow in the soup_filter_input_stream_read_until() function causes a heap buffer over-read when parsing multipart HTTP responses. A malicious HTTP server can exploit this by sending a crafted multipart response, potentially causing the client application to crash or disclose sensitive heap memory.
Weintek cMT3092X HMI allows a non-privileged user to modify tokens to escalate privileges.
Weintek cMT3092X HMI stores user account passwords in plaintext.