Comparison Overview
Purity Cosmetics (100% PURE)
Purity Cosmetics (100% PURE)
2221 Oakland Road, San Jose, 95131, US
Last Update: 31/01/2026
Purity Cosmetics is a fast growing prestige cosmetic company managing and launching brands including our flagship brand, 100% Pure. Inspired by her garden, product developer Susie Wang created 100% Pure Cosmetics to complement her healthy lifestyle. Made with pigments f...
Coty
Buitenveldertselaan 3-5, Amsterdam, 1082, NL
Last Update: 03/04/2026
Since 1904, Coty has fearlessly pioneered innovation across the beauty industry. We have a reputation for breaking new ground; a history of ‘firsts’ and ‘bests’ that has laid the foundation for the industry as we know it today. For over a century, our brands have been ...
Compliance Ranges Comparison
Purity Cosmetics (100% PURE)
Coty
Benchmark & Cyber Underwriting Signals
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Purity Cosmetics (100% PURE) in 2026.
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Coty in 2026.
Incident History - Purity Cosmetics (100% PURE) (X = Date, Y = Severity)
Purity Cosmetics (100% PURE) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Coty (X = Date, Y = Severity)
Coty cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Purity Cosmetics (100% PURE)
Coty
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: *.*.