Comparison Overview
Mobil Lubricants Europe
Mobil Lubricants Europe
Hermeslaan 2, Machelen, 1831, BE
Last Update: 10/01/2026
Competition in your sector has never been so intense. You need solutions to cut costs, boost efficiency and meet changing regulations, without compromising on performance. Whether you are in energy or general manufacturing, fleet or mining sectors, you need these soluti...
Shell
York Road, London, SE1 7NA, GB
Last Update: 02/07/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
Mobil Lubricants Europe
Shell
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Mobil Lubricants Europe in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
Shell has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Mobil Lubricants Europe (X = Date, Y = Severity)
Mobil Lubricants Europe 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
Mobil Lubricants Europe
Shell
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.