Comparison Overview
FPL Energy Services, Inc.
FPL Energy Services, Inc.
N/A
Last Update: 25/02/2026
FPL Energy Services, Inc. is a leading provider of reliable solutions for Florida businesses and governmental customers. Headquartered in South Florida, FPL Energy Services is an unregulated subsidiary of Florida Power & Light Company (a NextEra Energy Company), the thi...
Suncor
150 - 6 Avenue SW, Calgary, CA
Last Update: 01/04/2026
In 1967, we pioneered commercial development of Canada's oil sands – one of the largest petroleum resource basins in the world. Since then, Suncor has grown to become a globally competitive integrated energy company with a balanced portfolio of high-quality assets, a st...
Compliance Ranges Comparison
FPL Energy Services, Inc.
Suncor
Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for FPL Energy Services, Inc. in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Suncor in 2026.
Incident History - FPL Energy Services, Inc. (X = Date, Y = Severity)
FPL Energy Services, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Suncor (X = Date, Y = Severity)
Suncor cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
FPL Energy Services, Inc.
Suncor
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: *.*.