Comparison Overview
IEEE Standards Association | IEEE SA

IEEE Standards Association | IEEE SA
445 Hoes Lane, Piscataway, NJ, 08854, US
Last Update: 30/03/2026
The IEEE Standards Association (IEEE SA) is a leading consensus building organization that nurtures, develops, and advances global technologies. Providing a neutral and open platform to empower innovators across borders and disciplines, IEEE SA facilitates standards dev...

International Committee of the Red Cross - ICRC
19, avenue de la Paix, Geneva, 1202, CH
Last Update: 14/09/2026
Established in 1863, the International Committee of the Red Cross (ICRC) works worldwide to provide humanitarian help for people affected by conflict and armed violence and to promote the laws that protect victims of war. An independent and neutral organization, its man...
Compliance Ranges Comparison

IEEE Standards Association | IEEE SA







International Committee of the Red Cross - ICRC






Benchmark & Cyber Underwriting Signals
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for IEEE Standards Association | IEEE SA in 2026.
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for International Committee of the Red Cross - ICRC in 2026.
Incident History - IEEE Standards Association | IEEE SA (X = Date, Y = Severity)
IEEE Standards Association | IEEE SA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - International Committee of the Red Cross - ICRC (X = Date, Y = Severity)
International Committee of the Red Cross - ICRC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

IEEE Standards Association | IEEE SA

International Committee of the Red Cross - ICRC
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.