Comparison Overview
U.S. Department of Health and Human Services (HHS)

U.S. Department of Health and Human Services (HHS)
200 Independence Avenue S.W., Washington, District of Columbia, US, 20201
Last Update: 05/10/2026
The Department of Health and Human Services (HHS) is the United States government's principal agency for protecting the health of all Americans and providing essential human services, especially for those who are least able to help themselves.

GSA
1800 F St. NW, Washington, 20405, US
Last Update: 31/03/2026
General Services Administration (GSA) is an independent agency of the United States government established in 1949 to help manage and support the basic functioning of federal agencies. Our organization includes the Public Buildings Service (PBS), Federal Acquisition Ser...
Compliance Ranges Comparison

U.S. Department of Health and Human Services (HHS)







GSA






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
U.S. Department of Health and Human Services (HHS) has 102.7% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for GSA in 2026.
Incident History - U.S. Department of Health and Human Services (HHS) (X = Date, Y = Severity)
U.S. Department of Health and Human Services (HHS) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - GSA (X = Date, Y = Severity)
GSA cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

U.S. Department of Health and Human Services (HHS)

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