Comparison Overview
Gazprom Neft

Gazprom Neft
ул. Почтамтская, д. 3-5,, Санкт-Петербург, 190000,, RU
Last Update: 21/03/2026
Gazprom Neft is a technological leader in Russia’s oil and gas market. We produce high-quality fuels, lubricants and bitumens for business and retail customers, refuel aircraft, and are developing our filling-stations network. New technologies mean we are constantly imp...

repsol
Méndez Álvaro, 44, Madrid, Madrid, ES, 28045
Last Update: 14/09/2026
What do you do with the energy that drives you every day? We strive to turn it into something useful for you—your decisions and your next steps. We are a company that explores multi-energy solutions through innovation, technology, and the curiosity of our team. With ove...
Compliance Ranges Comparison

Gazprom Neft







repsol






Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Gazprom Neft in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for repsol in 2026.
Incident History - Gazprom Neft (X = Date, Y = Severity)
Gazprom Neft cyber incidents detection timeline including parent company and subsidiaries.
Incident History - repsol (X = Date, Y = Severity)
repsol cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Gazprom Neft

repsol
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.