Comparison Overview
Toray Membrane USA, Inc.
Toray Membrane USA, Inc.
13435 Danielson Street, Poway, CA, 92064, US
Last Update: 09/05/2026
In 2006 Toray Membrane USA, Inc. (TMUS) was formed as a subsidiary of Toray Industries. TMUS' capabilities include automated manufacturing of spiral-wound membrane elements for a comprehensive set of membrane technologies (RO, NF, UF, MF, MBR). Toray offers membrane co...
WM
800 Capitol St, Suite 3000, Houston, Texas, US, 77002
Last Update: 29/03/2026
WM is North America's leading provider of integrated environmental solutions. We partner with our customers and communities to manage and reduce waste from collection to disposal while recovering valuable resources and creating clean, renewable energy. We are on a quest...
Compliance Ranges Comparison
Toray Membrane USA, Inc.
WM
Benchmark & Cyber Underwriting Signals
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for Toray Membrane USA, Inc. in 2026.
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for WM in 2026.
Incident History - Toray Membrane USA, Inc. (X = Date, Y = Severity)
Toray Membrane USA, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - WM (X = Date, Y = Severity)
WM cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Toray Membrane USA, Inc.
WM
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: *.*.