Comparison Overview
Northeastern University

Northeastern University
360 Huntington Ave, Boston, MA, US, 02115-5005
Last Update: 01/04/2026
Founded in 1898, Northeastern is a global research university with a distinctive, experience-driven approach to education and discovery. The university is a leader in experiential learning, powered by the world’s most far-reaching cooperative education program. We inte...

Emory University
408 Administration Building, 201 Dowman Drive, Atlanta, GA, US, 30322
Last Update: 01/04/2026
Emory University, a top research university located in Atlanta, Georgia, is an inquiry-driven, ethically engaged and diverse community whose members work collaboratively for positive transformation in the world through courageous leadership in teaching, research, schola...
Compliance Ranges Comparison

Northeastern University







Emory University






Benchmark & Cyber Underwriting Signals
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Northeastern University in 2026.
Incidents vs Higher Education Industry Avg (This Year)
No incidents recorded for Emory University in 2026.
Incident History - Northeastern University (X = Date, Y = Severity)
Northeastern University cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Emory University (X = Date, Y = Severity)
Emory University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Northeastern University

Emory University
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.