Comparison Overview
Shepherd Power

Shepherd Power
10353 Richmond Ave, Houston, Texas, 77042, US
Last Update: 02/04/2026
We find solutions for industrial sites with limited reasonable options for reducing emissions while enhancing their business operations. By understanding our customers’ technical and commercial needs, we provide reliable, economical, emissions-free nuclear energy. A...

Saudi Electricity Company
Riyadh, SA
Last Update: 17/09/2026
The Saudi Electricity Company was established on the 5th of April in the year 2000, incorporated in accordance with Council of Ministers Mandate No. 169 dated November 30th, 1998, the Saudi Electricity Company was born out of the merger of smaller regional power company...
Compliance Ranges Comparison

Shepherd Power







Saudi Electricity Company






Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Shepherd Power in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Saudi Electricity Company in 2026.
Incident History - Shepherd Power (X = Date, Y = Severity)
Shepherd Power cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Saudi Electricity Company (X = Date, Y = Severity)
Saudi Electricity Company cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Shepherd Power

Saudi Electricity Company
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.