Comparison Overview
Greenlid Envirosciences
Greenlid Envirosciences
180 John St, Toronto, Ontario, M5T 1X5, CA
Last Update: 04/04/2026
Leading manufacturer for North America’s retailers and foodservice’s entire compostable disposables section with over 14,000 retail stores for private label, 10,000+ Greenlid brand and restaurants & foodservice. We take the guesswork out of single use plastic bans and c...
Vorwerk Group
Rauental 38, None, Wuppertal, North Rhine-Westphalia, DE, 42289
Last Update: 02/04/2026
For more than 140 years, Vorwerk has been an internationally active family-owned company focused on improving life everywhere we call home. Our superior products and services come with a human touch, from the way we develop and sell them, to the way they are used. Vorwe...
Compliance Ranges Comparison
Greenlid Envirosciences
Vorwerk Group
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Greenlid Envirosciences in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Vorwerk Group in 2026.
Incident History - Greenlid Envirosciences (X = Date, Y = Severity)
Greenlid Envirosciences cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vorwerk Group (X = Date, Y = Severity)
Vorwerk Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Greenlid Envirosciences
Vorwerk Group
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: *.*.