Comparison Overview
Unimed Pato Branco
Unimed Pato Branco
Rua Tamoio, 253, Pato Branco, Paraná, BR, 85501067
Last Update: 12/11/2025
A Unimed Pato Branco foi fundada em 2 de abril de 1990, por um grupo de médicos que ousou idealizar a construção de uma Cooperativa, para impulsionar a área da saúde, na região Sudoeste do Paraná. Hoje, com cerca de 300 cooperados, a Unimed Pato Branco é considerada um...
Young Living Essential Oils
1538 West Sandalwood Drive, Lehi, 84043-9572, US
Last Update: 30/03/2026
Through the painstaking steps of our proprietary Seed to Seal® production process, we produce the best, most authentic essential oils in the world. We are committed to providing pure, powerful products for every family and lifestyle, all infused with the life-changing b...
Compliance Ranges Comparison
Unimed Pato Branco
Young Living Essential Oils
Benchmark & Cyber Underwriting Signals
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Unimed Pato Branco in 2026.
Incidents vs Wellness and Fitness Services Industry Avg (This Year)
No incidents recorded for Young Living Essential Oils in 2026.
Incident History - Unimed Pato Branco (X = Date, Y = Severity)
Unimed Pato Branco cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Young Living Essential Oils (X = Date, Y = Severity)
Young Living Essential Oils cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Unimed Pato Branco
Young Living Essential Oils
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: *.*.