Comparison Overview
AbbVie | Deutschland
AbbVie | Deutschland
Mainzer Straße 81, Wiesbaden, Hessen, DE, 65189
Last Update: 04/03/2026
AbbVie ist ein forschendes BioPharma-Unternehmen, in Deutschland mit rund 3.500 Mitarbeiter*innen an seinem Hauptsitz in Wiesbaden und seinem Forschungs- und Produktionsstandort in Ludwigshafen vertreten. Unsere Mission ist es, innovative Therapien zu erforschen, die e...
AUROBINDO PHARMA LTD
Galaxy, Floors: 22-24, Plot No.1, Survey No.83/1, Hyderabad Knowledge City, Raidurg Panmaktha, Ranga Reddy District,, Hyderabad, 500032, IN
Last Update: 03/04/2026
Aurobindo Pharma Limited (NSE: AUROPHARMA, BSE: 524804, Reuters: ARBN.NS, Bloomberg: ARBP IN) is an integrated global pharmaceutical company headquartered in Hyderabad, India. The Company develops, manufactures, and markets a wide range of generic pharmaceuticals, brand...
Compliance Ranges Comparison
AbbVie | Deutschland
AUROBINDO PHARMA LTD
Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for AbbVie | Deutschland in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for AUROBINDO PHARMA LTD in 2026.
Incident History - AbbVie | Deutschland (X = Date, Y = Severity)
AbbVie | Deutschland cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AUROBINDO PHARMA LTD (X = Date, Y = Severity)
AUROBINDO PHARMA LTD cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AbbVie | Deutschland
AUROBINDO 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: *.*.