Comparison Overview
SC Johnson Lifestyle Brands
SC Johnson Lifestyle Brands
631 Howard St, San Francisco, California, 94105, US
Last Update: 01/04/2026
SC Johnson Lifestyle Brands (the LSB) is a growing house of like-minded brands under the SC Johnson umbrella including method, Mrs. Meyer’s Clean Day, babyganics and Ecover. Headquartered in San Francisco with additional operations in Chicago and throughout Europe, the ...
the LEGO Group
Aastvej 1, Billund, DK, 7190
Last Update: 29/03/2026
We are the LEGO Group, the company behind the world’s most loved LEGO® bricks. Our brand name derived from the two Danish words Leg Godt, which mean “Play Well”. We’ve been sparking imaginations and inspiring the builders of tomorrow since 1932. This is our mission an...
Compliance Ranges Comparison
SC Johnson Lifestyle Brands
the LEGO Group
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for SC Johnson Lifestyle Brands in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for the LEGO Group in 2026.
Incident History - SC Johnson Lifestyle Brands (X = Date, Y = Severity)
SC Johnson Lifestyle Brands cyber incidents detection timeline including parent company and subsidiaries.
Incident History - the LEGO Group (X = Date, Y = Severity)
the LEGO Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SC Johnson Lifestyle Brands
the LEGO 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: *.*.