Comparison Overview
Save the Children US

Save the Children US
501 Kings Highway East, Fairfield, 06825, US
Last Update: 29/03/2026
Save the Children is the leading independent organization creating lasting change in the lives of children in need in the United States and around the world. Recognized for our commitment to accountability, innovation and collaboration, our work takes us into the heart ...

American Red Cross
430 17th St NW, Washington, 20006, US
Last Update: 05/04/2026
The American Red Cross prevents and alleviates human suffering in the face of emergencies by mobilizing the power of volunteers and the generosity of donors. Each day, thousands of people – people just like you – provide compassionate care to those in need. Our networ...
Compliance Ranges Comparison

Save the Children US







American Red Cross






Benchmark & Cyber Underwriting Signals
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for Save the Children US in 2026.
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for American Red Cross in 2026.
Incident History - Save the Children US (X = Date, Y = Severity)
Save the Children US cyber incidents detection timeline including parent company and subsidiaries.
Incident History - American Red Cross (X = Date, Y = Severity)
American Red Cross cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Save the Children US

American Red Cross
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.