Comparison Overview
EMS
EMS
Rodovia Jorn. Francisco Aguirre Proenca, Hortolandia, 13186-525, BR
Last Update: 01/04/2026
Fundada há mais de 60 anos e com capital 100% nacional, a EMS é a líder do mercado farmacêutico brasileiro há 19 anos consecutivos, pertencente ao Grupo NC, um dos maiores conglomerados brasileiros. A empresa ocupa também a liderança no segmento de genéricos desde 2013...
Novartis
Novartis Campus, Basel, 4002, CH
Last Update: 20/05/2026
Novartis is an innovative medicines company. Every day, working to reimagine medicine to improve and extend people’s lives so that patients, healthcare professionals and societies are empowered in the face of serious disease. Our medicines reach more than 250 million pe...
Compliance Ranges Comparison
EMS
Novartis
Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for EMS in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
Novartis has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - EMS (X = Date, Y = Severity)
EMS cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Novartis (X = Date, Y = Severity)
Novartis cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
EMS
Novartis
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: *.*.