Comparison Overview
Telesign

Telesign
13274 Fiji Way Marina, Marina del Rey, 90292, US
Last Update: 02/04/2026
Telesign, a part of the Proximus Group, provides Continuous Trust™ to leading global enterprises by connecting, protecting, and defending their digital identities. Telesign verifies over five billion unique phone numbers a month, representing half of the world’s mobile ...

Gainwell Technologies
United States, US
Last Update: 09/10/2026
The people who build careers at Gainwell Technologies share one thing: they want their work to matter. Here, it does. We're the essential ingredient that makes Medicaid work. For more than 50 years, we've combined our sweeping scale and technology to turn complex polic...
Compliance Ranges Comparison

Telesign







Gainwell Technologies






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Telesign in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Gainwell Technologies has 96.08% more incidents than the average of all companies with at least one recorded incident.
Incident History - Telesign (X = Date, Y = Severity)
Telesign cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Gainwell Technologies (X = Date, Y = Severity)
Gainwell Technologies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Telesign

Gainwell Technologies
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.