Comparison Overview
Capgemini Life Sciences and Healthcare

Capgemini Life Sciences and Healthcare
Paris, FR
Last Update: 05/12/2025
Capgemini is a global leader in consulting, digital transformation, technology, and engineering services. The Group is at the forefront of innovation to address the entire breadth of clients’ opportunities in the evolving world of cloud, digital, and platforms. With o...

inDrive
Mountain View, 94040, US
Last Update: 03/09/2026
inDrive is a global mobility and urban services platform. The inDrive app has been downloaded over 400 million times, and has been the second most downloaded mobility app for the third consecutive year. In addition to ride-hailing, inDrive provides an expanding list of ...
Compliance Ranges Comparison

Capgemini Life Sciences and Healthcare







inDrive






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Capgemini Life Sciences and Healthcare in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for inDrive in 2026.
Incident History - Capgemini Life Sciences and Healthcare (X = Date, Y = Severity)
Capgemini Life Sciences and Healthcare cyber incidents detection timeline including parent company and subsidiaries.
Incident History - inDrive (X = Date, Y = Severity)
inDrive cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Capgemini Life Sciences and Healthcare

inDrive
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.