Comparison Overview
Kao Corporation
Kao Corporation
1-14-10, Nihonbashi Kayabacho, Tokyo, Kanto, 103-8210, JP
Last Update: 30/12/2025
Ever since the company's founding in 1887, Kao has strived to deliver value to the life of people everywhere in the world. Today, we are a leading manufacturer in the fields of hygiene, beauty and health, while our chemical business contributes to the development of div...
Beiersdorf
Unnastraße 48, Hamburg, 20253, DE
Last Update: 05/04/2026
Beiersdorf has been a pioneer in innovative, high-quality skin care products and groundbreaking skin research for over 140 years. Our internationally beloved brands, including NIVEA – the world’s no. 1 skin care brand –, Eucerin, Hansaplast, La Prairie and Chantecaille,...
Compliance Ranges Comparison
Kao Corporation
Beiersdorf
Benchmark & Cyber Underwriting Signals
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Kao Corporation in 2026.
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Beiersdorf in 2026.
Incident History - Kao Corporation (X = Date, Y = Severity)
Kao Corporation cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Beiersdorf (X = Date, Y = Severity)
Beiersdorf cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Kao Corporation
Beiersdorf
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: *.*.