Comparison Overview
Bernhard Schulte Shipmanagement
Bernhard Schulte Shipmanagement
Vorsetzen 54, Hamburg, Hamburg, DE, 20459
Last Update: 04/04/2026
Bernhard Schulte Shipmanagement (BSM) is an integrated maritime solutions provider. Managing a fleet of over 650 vessels, 20,000 seafarers and 2,000 shore-based employees enable the delivery of safe, reliable and efficient ship management services through a network of 1...
Anglo-Eastern
17/F Kingston International Centre, 19 Wang Chiu Road, Kowloon Bay, Kowloon, Hong Kong, ., HK
Last Update: 03/04/2026
Anglo-Eastern's rich maritime heritage spans over 50 years of ship management, crew management, cruise & leisure management and technical services. We manage a diverse fleet of vessels worldwide on behalf of our global partners, and uniquely offer both cadet and crew tr...
Compliance Ranges Comparison
Bernhard Schulte Shipmanagement
Anglo-Eastern
Benchmark & Cyber Underwriting Signals
Incidents vs Maritime Transportation Industry Avg (This Year)
No incidents recorded for Bernhard Schulte Shipmanagement in 2026.
Incidents vs Maritime Transportation Industry Avg (This Year)
No incidents recorded for Anglo-Eastern in 2026.
Incident History - Bernhard Schulte Shipmanagement (X = Date, Y = Severity)
Bernhard Schulte Shipmanagement cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Anglo-Eastern (X = Date, Y = Severity)
Anglo-Eastern cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Bernhard Schulte Shipmanagement
Anglo-Eastern
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: *.*.