Comparison Overview
Toray Membrane Europe AG
Toray Membrane Europe AG
Grabenackerstrasse 8b Muenchenstein, 4142, CH
Last Update: 31/10/2025
TORAY is leading the way to a sustainable future with our innovative membrane technologies that produce clean water and recover valuable. resources. TORAY Reverse Osmosis and Nanofiltration spiral wound membrane elements have been produced since 1968, starting with cel...
Siemens Gamesa
Parque Tecnológico de Bizkaia, edificio 222, Zamudio, 48170, ES
Last Update: 01/04/2026
Siemens Gamesa is a global technology leader in the renewable energy industry - specifically in the development, manufacturing, installation and maintenance of wind turbines. Being a pioneer in renewables since the 1980s, we put our scale and entrepreneurial culture to ...
Compliance Ranges Comparison
Toray Membrane Europe AG
Siemens Gamesa
Benchmark & Cyber Underwriting Signals
Incidents vs Renewable Energy Semiconductor Manufacturing Industry Avg (This Year)
No incidents recorded for Toray Membrane Europe AG in 2026.
Incidents vs Renewable Energy Semiconductor Manufacturing Industry Avg (This Year)
No incidents recorded for Siemens Gamesa in 2026.
Incident History - Toray Membrane Europe AG (X = Date, Y = Severity)
Toray Membrane Europe AG cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Siemens Gamesa (X = Date, Y = Severity)
Siemens Gamesa cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Toray Membrane Europe AG
Siemens Gamesa
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: *.*.