Comparison Overview
Prudential Financial

Prudential Financial
Broad St, Newark, New Jersey, US, 07102
Last Update: 20/09/2026
Prudential Financial (NYSE:PRU) was founded on the belief that financial security should be within reach for everyone, and for over 140 years, we have helped our customers reach their potential and tackle life's challenges for now and future generations to come. Today, ...

Santander US
75 State Street, Boston, 02109, US
Last Update: 12/09/2026
Santander’s purpose is to help people and businesses prosper. In the United States, Santander is a leading financial services provider with approximately 11,000 employees, 4.3 million customers, and assets of $243 billion, as of Q4 2025. Our five diverse and growing bu...
Compliance Ranges Comparison

Prudential Financial







Santander US






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Prudential Financial in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Santander US in 2026.
Incident History - Prudential Financial (X = Date, Y = Severity)
Prudential Financial cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Santander US (X = Date, Y = Severity)
Santander US cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Prudential Financial

Santander US
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.