Comparison Overview
Algenist
Algenist
500 N Brand Blvd, Glendale, California, 91203, US
Last Update: 01/03/2026
ALGENIST was born from biotechnology, the innovative green science respecting nature, to uncover the limitless potential of algae. Alguronic Acid, ALGENIST’s patented and exclusive star ingredient is naturally sourced and sustainably produced and used in every single AL...
Natura
Av. Alexandre Colares, 1.188, Vila Jaguara, São Paulo, São Paulo, BR, 05106-0000
Last Update: 28/03/2026
Founded in 1969, Natura is a Brazilian multinational in the cosmetics and personal care segment, a leader in direct sales in Brazil, and recognized for protecting the Amazon social biodiversity through its sustainable business model. Cruelty free. 100% vegan. With 7,000...
Compliance Ranges Comparison
Algenist
Natura
Benchmark & Cyber Underwriting Signals
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Algenist in 2026.
Incidents vs Personal Care Product Manufacturing Industry Avg (This Year)
No incidents recorded for Natura in 2026.
Incident History - Algenist (X = Date, Y = Severity)
Algenist cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Natura (X = Date, Y = Severity)
Natura cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Algenist
Natura
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: *.*.