Comparison Overview
WORMS Safety
WORMS Safety
Quarry Bay , Hong Kong, 999077, HK
Last Update: 06/12/2025
WORMS Safety Group is the first alliance of quality management specialists in their fields of product expertise that enables customers to meet their compliance goals, while managing risk and identifying disruption for growth through inspection, testing, auditing, certi...
Marubeni Corporation
4-2, Ohtemachi 1-chome, Chiyoda-ku, 1008088, JP
Last Update: 03/04/2026
Marubeni Corporation (TSE securities code: 8002) is one of Japan’s largest trading companies (sogo shosha) with more than 165 years of history. Headquartered in Tokyo, Marubeni continues to expand its businesses across the globe, with 130 branches and offices worldwide....
Compliance Ranges Comparison
WORMS Safety
Marubeni Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for WORMS Safety in 2026.
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for Marubeni Corporation in 2026.
Incident History - WORMS Safety (X = Date, Y = Severity)
WORMS Safety cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Marubeni Corporation (X = Date, Y = Severity)
Marubeni Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
WORMS Safety
Marubeni Corporation
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: *.*.