Comparison Overview
Baltimore Gas and Electric
Baltimore Gas and Electric
Baltimore, 21201, US
Last Update: 20/03/2026
BGE, headquartered in Baltimore, is Maryland’s largest gas and electric utility, delivering power to more than 1.3 million electric customers and more than 700,000 natural gas customers in Central Maryland. The company’s approximately 3,200 employees are committed to th...
National Grid
1–3 Strand, London, WC2N 5EH, GB
Last Update: 07/05/2026
National Grid lies at the heart of a transforming energy system. Our business areas play a vital role in connecting millions of people to the energy they use, while continually seeking ways to make the energy system clean, fair, and affordable. In the UK we own and de...
Compliance Ranges Comparison
Baltimore Gas and Electric
National Grid
Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for Baltimore Gas and Electric in 2026.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for National Grid in 2026.
Incident History - Baltimore Gas and Electric (X = Date, Y = Severity)
Baltimore Gas and Electric cyber incidents detection timeline including parent company and subsidiaries.
Incident History - National Grid (X = Date, Y = Severity)
National Grid cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Baltimore Gas and Electric
National Grid
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: *.*.