Comparison Overview
Port of Longview
Port of Longview
10 International Way, Longview, Washington, US, 98632
Last Update: 30/03/2026
Sixty-six miles from the Pacific Ocean in Southwest Washington, you will find the Port of Longview. A port with a mission to excel in international and domestic trade through superior labor and strategic investments. The Port sprawls across 835 acres of land and is situ...
Hapag-Lloyd AG
Ballindamm 25, Hamburg, DE, 20095
Last Update: 01/04/2026
About Hapag-Lloyd With a fleet of 313 modern container ships and a total transport capacity of 2.5 million TEU, Hapag-Lloyd is one of the world’s leading liner shipping companies. In the Liner Shipping segment, the Company has around 14,000 employees and 400 offices in ...
Compliance Ranges Comparison
Port of Longview
Hapag-Lloyd AG
Benchmark & Cyber Underwriting Signals
Incidents vs Maritime Transportation Industry Avg (This Year)
No incidents recorded for Port of Longview in 2026.
Incidents vs Maritime Transportation Industry Avg (This Year)
No incidents recorded for Hapag-Lloyd AG in 2026.
Incident History - Port of Longview (X = Date, Y = Severity)
Port of Longview cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hapag-Lloyd AG (X = Date, Y = Severity)
Hapag-Lloyd AG cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Port of Longview
Hapag-Lloyd AG
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: *.*.