Comparison Overview
UPMC Health Plan

UPMC Health Plan
600 Grant St, None, Pittsburgh, Pennsylvania, US, 15219
Last Update: 19/03/2026
How can we best serve our members and the community? UPMC Health Plan responds to that question by providing Quality, Choice, Access, Service, and Value. As the second-largest health insurer in western Pa., we serve nearly half a million members and offer a full...

AIA
AIA Central, Central, N/A, HK
Last Update: 07/10/2026
AIA Group Limited and its subsidiaries (collectively “AIA” or the “Group”) comprise the largest independent publicly listed pan-Asian life insurance group. It has a presence in 18 markets – wholly-owned branches and subsidiaries in Mainland China, Hong Kong SAR(1), Thai...
Compliance Ranges Comparison

UPMC Health Plan







AIA






Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for UPMC Health Plan in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for AIA in 2026.
Incident History - UPMC Health Plan (X = Date, Y = Severity)
UPMC Health Plan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AIA (X = Date, Y = Severity)
AIA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

UPMC Health Plan

AIA
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.