Comparison Overview
Novartis Magyarország
Novartis Magyarország
Bartók Béla út 43-47., Budapest, 1114, HU
Last Update: 20/03/2026
A Novartisnál újragondoljuk az orvoslást azért, hogy jobbá tegyük és meghosszabbítsuk az emberek életét. Világszinten vezető egészségügyi vállalatként a tudományos alapokon nyugvó innovációt ötvözzük a digitális technológiai megoldásokkal azért, hogy olyan terápiákat ho...
Alembic Pharmaceuticals Limited
Alembic Road, Vadodara, 390003, IN
Last Update: 01/04/2026
Established in 1907, Alembic Pharmaceuticals Limited is a leading pharmaceutical company in India. The Company is vertically integrated with the ability to develop, manufacture and market pharmaceutical products, pharmaceutical substances and Intermediates. Alembic is t...
Compliance Ranges Comparison
Novartis Magyarország
Alembic Pharmaceuticals Limited
Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Novartis Magyarország in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Alembic Pharmaceuticals Limited in 2026.
Incident History - Novartis Magyarország (X = Date, Y = Severity)
Novartis Magyarország cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Alembic Pharmaceuticals Limited (X = Date, Y = Severity)
Alembic Pharmaceuticals Limited cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Novartis Magyarország
Alembic Pharmaceuticals Limited
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: *.*.