Comparison Overview
Novo Nordisk
Novo Nordisk
Novo Alle, Bagsværd, DK, 2880
Last Update: 20/06/2026
We’re not your typical healthcare company. In a modern world of quick fixes, we focus on solutions to defeat serious chronic disease and create long-term health. Our unordinary mindset is at the heart of everything we do. We seek out new ideas and put people first as we...
Zoetis
10 Sylvan Way, Parsippany, NJ, US, 07054
Last Update: 04/04/2026
The world’s leading animal health company. We’ve been innovating ways to predict, prevent, detect, and treat animal illness for over 70 years, and we continue to stand by those raising and caring for animals worldwide – from veterinarians and pet owners to livestock far...
Compliance Ranges Comparison
Novo Nordisk
Zoetis
Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
Novo Nordisk has 96.08% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Zoetis in 2026.
Incident History - Novo Nordisk (X = Date, Y = Severity)
Novo Nordisk cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Zoetis (X = Date, Y = Severity)
Zoetis cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Novo Nordisk
Zoetis
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: *.*.