Comparison Overview
iOttie Inc.
iOttie Inc.
Midtown, None, New York, New York, US, None
Last Update: 02/04/2026
Based in the busy city of New York, iOttie was founded in 2010 and has since become a thriving company within the electronics industry. Our team strives to produce products that are innovative, creative and unique while maintaining high quality. Since 2010, we have bee...
Whirlpool Corporation
2000 North M63, Benton Harbor, Michigan, US, 49022
Last Update: 29/03/2026
Life at home has been at the heart of our business for 110+ years - it is why we exist and why we are passionate about what we do. Beginning with our founders to the everyday actions of our people, our values have always kept us grounded -- Integrity, Respect, Inclusion...
Compliance Ranges Comparison
iOttie Inc.
Whirlpool Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for iOttie Inc. in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Whirlpool Corporation in 2026.
Incident History - iOttie Inc. (X = Date, Y = Severity)
iOttie Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Whirlpool Corporation (X = Date, Y = Severity)
Whirlpool Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
iOttie Inc.
Whirlpool 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: *.*.