Comparison Overview
Burt's Bees
Burt's Bees
210 west pettigrew street, Durham, NC, 27701, US
Last Update: 12/03/2026
Burt's Bees is the #1 dermatologist recommended natural skin care brand, offering clean and consciously-crafted products to work with the skin and uplift the spirit. We believe that nature holds the key to healthy skin, so we create skin care formulas that are packed wi...
Colgate-Palmolive
300 Park Ave, New York, New York, US, 10022
Last Update: 29/03/2026
Make More Smiles. We are Colgate-Palmolive, a caring, innovative growth company that is reimagining a healthier future for all people, their pets and our planet. For over 200 years, we've poured our care into creating a future where everyone has more reasons to smile. C...
Compliance Ranges Comparison
Burt's Bees
Colgate-Palmolive
Benchmark & Cyber Underwriting Signals
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Burt's Bees in 2026.
Incidents vs Manufacturing Industry Avg (This Year)
No incidents recorded for Colgate-Palmolive in 2026.
Incident History - Burt's Bees (X = Date, Y = Severity)
Burt's Bees cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Colgate-Palmolive (X = Date, Y = Severity)
Colgate-Palmolive cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Burt's Bees
Colgate-Palmolive
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: *.*.