Comparison Overview
Resources for Human Development

Resources for Human Development
4700 Wissahickon Ave., Philadelphia, 19144, US
Last Update: 03/04/2026
Resources for Human Development is a comprehensive human services organization based in Philadelphia. Its mission is to empower the most vulnerable and marginalized members of society as they build the highest level of independence possible. RHD oversees and supports mo...

International Rescue Committee
122 E 42st , New York, NY, US, 10168
Last Update: 30/03/2026
The International Rescue Committee responds to the world’s worst humanitarian crises and help people to survive, recover, and gain control of their future. Founded in 1933 at the request of Albert Einstein, the IRC offers lifesaving care and life-changing assistance t...
Compliance Ranges Comparison

Resources for Human Development







International Rescue Committee






Benchmark & Cyber Underwriting Signals
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for Resources for Human Development in 2026.
Incidents vs Non-profit Organizations Industry Avg (This Year)
No incidents recorded for International Rescue Committee in 2026.
Incident History - Resources for Human Development (X = Date, Y = Severity)
Resources for Human Development cyber incidents detection timeline including parent company and subsidiaries.
Incident History - International Rescue Committee (X = Date, Y = Severity)
International Rescue Committee cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Resources for Human Development

International Rescue Committee
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.