Comparison Overview
Fieldwood Energy E&P México
Fieldwood Energy E&P México
Calle Jaime Balmes 8, Miguel Hidalgo, Mexico City, 11510, MX
Last Update: 21/03/2026
Fieldwood Energy E&P Mexico is a Mexican company established in 2015 to carry out exploration and production of hydrocarbons within the framework of energy sector legislation, is the operator of the contract with the Mexican state for the extraction of hydrocarbons unde...
ExxonMobil
US
Last Update: 26/06/2026
The need for energy is universal. That's why ExxonMobil scientists and engineers are pioneering new research and pursuing new technologies to reduce emissions while creating more efficient fuels. We're committed to responsibly meeting the world's energy needs. We aim...
Compliance Ranges Comparison
Fieldwood Energy E&P México
ExxonMobil
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Fieldwood Energy E&P México in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for ExxonMobil in 2026.
Incident History - Fieldwood Energy E&P México (X = Date, Y = Severity)
Fieldwood Energy E&P México cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ExxonMobil (X = Date, Y = Severity)
ExxonMobil cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Fieldwood Energy E&P México
ExxonMobil
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: *.*.