Comparison Overview
Novartis México

Novartis México
Insurgentes Sur 2475, Ciudad de Mexico, 01090 , MX
Last Update: 01/03/2026
Novartis Farmacéutica, S.A. de C.V. es individualmente “Responsable” de recabar sus datos personales, con domicilio en Av. Insurgentes Sur 2475, Tizapán San Ángel, Álvaro Obregón, 01090 Ciudad de México. Los datos personales que usted nos proporcione serán utilizados pa...

AbbVie
1 Waukegan Road, North Chicago, 60064, US
Last Update: 07/10/2026
AbbVie is a global biopharmaceutical company focused on creating medicines and solutions that put impact first — for patients, communities, and our world. We aim to address complex health issues and enhance people's lives through our core therapeutic areas: immunology, ...
Compliance Ranges Comparison

Novartis México







AbbVie






Benchmark & Cyber Underwriting Signals
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
No incidents recorded for Novartis México in 2026.
Incidents vs Pharmaceutical Manufacturing Industry Avg (This Year)
AbbVie has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Novartis México (X = Date, Y = Severity)
Novartis México cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AbbVie (X = Date, Y = Severity)
AbbVie cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Novartis México

AbbVie
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.