Comparison Overview
Vår Energi

Vår Energi
Vestre Svanholmen 1 Sandnes, Rogaland 4313, NO
Last Update: 27/10/2025
Vår Energi is a leading independent upstream oil and gas company on the Norwegian continental shelf (NCS). We are committed to deliver a better future through responsible value driven growth based on over 50 years of NCS operations, a robust and diversified asset portfo...

Shell
York Road, London, SE1 7NA, GB
Last Update: 07/10/2026
Shell is a global group of energy and petrochemical companies, employing 96,000 people across 70+ countries. We serve around 1 million commercial and industrial customers, and around 33 million customers daily at our Shell-branded retail service stations. Our purpose i...
Compliance Ranges Comparison

Vår Energi







Shell






Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Vår Energi in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
Shell has 296.04% more incidents than the average of all companies with at least one recorded incident.
Incident History - Vår Energi (X = Date, Y = Severity)
Vår Energi cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Shell (X = Date, Y = Severity)
Shell cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Vår Energi

Shell
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.