Comparison Overview

University of Cambridge

VS

CNRS

University of Cambridge

The Old Schools, Trinity Lane, Cambridge, England, GB, CB2 1TN
Last Update: 2026-04-04
View Profile
Between 750 and 799
https://www.cam.ac.uk/

The University of Cambridge is one of the world's foremost research universities. The University is made up of 31 Colleges and over 150 departments, faculties, schools and other institutions. Its mission is 'to contribute to society through the pursuit of education, learning, and research at the highest international levels of excellence'​.

NAICS: 5417
NAICS Definition: Scientific Research and Development Services
Employees: 19,890
Subsidiaries: 4
12-month incidents
0
Known data breaches
1
Attack type number
1
View Profile

CNRS

3 rue Michel-Ange, Paris, 75016, FR
Last Update: 2026-04-01
Between 750 and 799
https://www.cnrs.fr/

The French National Centre for Scientific Research is among the world's leading research institutions. Its scientists explore the living world, matter, the Universe, and the functioning of human societies in order to meet the major challenges of today and tomorrow. Internationally recognised for the excellence of its scientific research, the CNRS is a reference in the world of research and development, as well as for the general public.

NAICS: 5417
NAICS Definition: Scientific Research and Development Services
Employees: 22,365
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/university-of-cambridge.jpeg
University of Cambridge
—
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/cnrs.jpeg
CNRS
—
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
University of Cambridge
100%
Compliance Rate
0/4 Standards Verified
CNRS
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Research Services Industry Average (This Year)

No incidents recorded for University of Cambridge in 2026.

Incidents vs Research Services Industry Average (This Year)

No incidents recorded for CNRS in 2026.

Incident History — University of Cambridge (X = Date, Y = Severity)

University of Cambridge cyber incidents detection timeline including parent company and subsidiaries

Incident History — CNRS (X = Date, Y = Severity)

CNRS cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/university-of-cambridge.jpeg
University of Cambridge
Incidents

Date Detected: 09/2018
Type:Breach
Attack Vector: Phishing, Spoofed Websites
Motivation: Financial Gain, Espionage
Blog: Blog
https://images.rankiteo.com/companyimages/cnrs.jpeg
CNRS
Incidents

No Incident

FAQ

CNRS company demonstrates a stronger AI Cybersecurity Score compared to University of Cambridge company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

University of Cambridge company has historically faced a number of disclosed cyber incidents, whereas CNRS company has not reported any.

In the current year, CNRS company and University of Cambridge company have not reported any cyber incidents.

Neither CNRS company nor University of Cambridge company has reported experiencing a ransomware attack publicly.

University of Cambridge company has disclosed at least one data breach, while the other CNRS company has not reported such incidents publicly.

Neither CNRS company nor University of Cambridge company has reported experiencing targeted cyberattacks publicly.

Neither University of Cambridge company nor CNRS company has reported experiencing or disclosing vulnerabilities publicly.

Neither University of Cambridge nor CNRS holds any compliance certifications.

Neither company holds any compliance certifications.

University of Cambridge company has more subsidiaries worldwide compared to CNRS company.

CNRS company employs more people globally than University of Cambridge company, reflecting its scale as a Research Services.

Neither University of Cambridge nor CNRS holds SOC 2 Type 1 certification.

Neither University of Cambridge nor CNRS holds SOC 2 Type 2 certification.

Neither University of Cambridge nor CNRS holds ISO 27001 certification.

Neither University of Cambridge nor CNRS holds PCI DSS certification.

Neither University of Cambridge nor CNRS holds HIPAA certification.

Neither University of Cambridge nor CNRS 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