Comparison Overview
Novartis Serbia
Novartis Serbia
Ulica Omladinskih brigada 90a, Belgrade, undefined, 11070, RS
Last Update: 07/12/2025
Novartis je inovativna farmaceutska kompanija. Svakodnevno radimo na tome da pronađemo i unapredimo medicinska otkrića u cilju poboljšanja kvaliteta i dužine ljudskih života, i kako bismo osnažili pacijente, zdravstvene radnike i države u borbi sa ozbiljnim oboljenjima....
MANKIND PHARMA LTD
Phase 3, New Delhi, IN
Last Update: 04/04/2026
Mankind Pharma, one of the top 5 leading pharmaceutical companies in India, started its journey in 1995. Today, we have an employee base of over 20,000 and are racing towards $1 Billion. At Mankind, we aspire to aid the community in leading a healthy life by formulating...
Compliance Ranges Comparison
Novartis Serbia
MANKIND PHARMA LTD
Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Novartis Serbia in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for MANKIND PHARMA LTD in 2026.
Incident History - Novartis Serbia (X = Date, Y = Severity)
Novartis Serbia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - MANKIND PHARMA LTD (X = Date, Y = Severity)
MANKIND PHARMA LTD cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Novartis Serbia
MANKIND PHARMA LTD
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: *.*.