Comparison Overview

Celesio AG

VS

AbbVie

Celesio AG

Stockholmer Platz 1, Stuttgart, 70180
Last Update: 2026-04-04
View Profile
Between 800 and 849
http://www.mckesson.eu

On 12 September 2017, Celesio AG has officially announced its renaming to McKesson Europe AG, based on the shareholders’ decision at the Annual General Meeting 2017. Documents of Celesio AG remain documents of McKesson Europe AG. More information can be found in the press release"Renaming: Celesio AG becomes McKesson Europe AG"​: http://www.mckesson.eu/mck-en/news-press/releases-mckessoneurope/renaming--celesio-ag-becomes-mckesson-europe-ag/29600 Please refer to our new company site: http://www.linkedin.com/company/mckesson-europe Imprint: McKesson Europe AG Stockholmer Platz 1 70173 Stuttgart (Germany) Telephone: +49 711 5001-00 Telefax: +49 711 5001-1260 [email protected] http://www.facebook.com/mckessoneurope http://twitter.com/mckessoneurope

NAICS: 3254
NAICS Definition: Pharmaceutical and Medicine Manufacturing
Employees: 100
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

AbbVie

1 Waukegan Road, North Chicago, 60064, US
Last Update: 2026-04-02
Between 800 and 849
http://www.abbvie.com

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, oncology, neuroscience, eye care, aesthetics and other areas of unmet need. Learn more about us at www.abbvie.com and review our community guidelines at https://www.abbvie.com/social-media-community-guidelines.html.

NAICS: 3254
NAICS Definition: Pharmaceutical and Medicine Manufacturing
Employees: 60,650
Subsidiaries: 15
12-month incidents
0
Known data breaches
1
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/celesio-ag.jpeg
Celesio AG
—
ISO 27001
ISO 27001 certification not verified
Not verified
—
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
—
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
—
GDPR
GDPR certification not verified
Not verified
—
PCI DSS
PCI DSS certification not verified
Not verified
—
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/abbvie.jpeg
AbbVie
—
ISO 27001
ISO 27001 certification not verified
Not verified
—
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
—
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
—
GDPR
GDPR certification not verified
Not verified
—
PCI DSS
PCI DSS certification not verified
Not verified
—
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Celesio AG
100%
Compliance Rate
0/4 Standards Verified
AbbVie
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for Celesio AG in 2026.

Incidents vs Pharmaceutical Manufacturing Industry Average (This Year)

No incidents recorded for AbbVie in 2026.

Incident History — Celesio AG (X = Date, Y = Severity)

Celesio AG 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

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/celesio-ag.jpeg
Celesio AG
Incidents

No Incident

https://images.rankiteo.com/companyimages/abbvie.jpeg
AbbVie
Incidents

Date Detected: 6/2023
Type:Breach
Attack Vector: Exploitation of Vulnerability
Motivation: Financial gain
Blog: Blog

FAQ

AbbVie company demonstrates a stronger AI Cybersecurity Score compared to Celesio AG company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

AbbVie company has historically faced a number of disclosed cyber incidents, whereas Celesio AG company has not reported any.

In the current year, AbbVie company and Celesio AG company have not reported any cyber incidents.

Neither AbbVie company nor Celesio AG company has reported experiencing a ransomware attack publicly.

AbbVie company has disclosed at least one data breach, while Celesio AG company has not reported such incidents publicly.

Neither AbbVie company nor Celesio AG company has reported experiencing targeted cyberattacks publicly.

Neither Celesio AG company nor AbbVie company has reported experiencing or disclosing vulnerabilities publicly.

Neither Celesio AG nor AbbVie holds any compliance certifications.

Neither company holds any compliance certifications.

AbbVie company has more subsidiaries worldwide compared to Celesio AG company.

AbbVie company employs more people globally than Celesio AG company, reflecting its scale as a Pharmaceutical Manufacturing.

Neither Celesio AG nor AbbVie holds SOC 2 Type 1 certification.

Neither Celesio AG nor AbbVie holds SOC 2 Type 2 certification.

Neither Celesio AG nor AbbVie holds ISO 27001 certification.

Neither Celesio AG nor AbbVie holds PCI DSS certification.

Neither Celesio AG nor AbbVie holds HIPAA certification.

Neither Celesio AG nor AbbVie holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 5.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
References
Description

PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
References
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
References