Comparison Overview
Kordia
Kordia
Level 3, 162 Victoria Street , Auckland, 1010, NZ
Last Update: 02/04/2026
Kordia is a leading provider of mission-critical technology solutions. Our expertise spans connectivity, infrastructure, cyber security, field services, media and broadcast; and safety of life services. Our team consists of almost 500 highly skilled consultants, cyber...
Lumen Technologies
Monroe, Louisiana , US, 71203
Last Update: 02/04/2026
Lumen connects the world. We digitally connect people, data and applications – quickly, securely and effortlessly. Everything we do at Lumen takes advantage of our network strength. From metro connectivity to long-haul data transport to our edge cloud, security, and man...
Compliance Ranges Comparison
Kordia
Lumen Technologies
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
Kordia has 46.24% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Lumen Technologies in 2026.
Incident History - Kordia (X = Date, Y = Severity)
Kordia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Lumen Technologies (X = Date, Y = Severity)
Lumen Technologies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Kordia
Lumen Technologies
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: *.*.