Comparison Overview
Vanderbilt University

Vanderbilt University
2201 West End Avenue, Nashville, Tennessee, US, 37235
Last Update: 12/09/2026
Vanderbilt University is a top-ranked teaching and research university in Nashville, Tennessee. Powered by collaboration. Follow Vanderbilt on Facebook, Twitter, TikTok and Instagram @VanderbiltU. See more Vanderbilt social media at https://social.vanderbilt.edu/ Loca...

Brigham Young University
Main Campus, Provo, UT, US, 84602
Last Update: 02/04/2026
We believe a world yearning for hope and joy needs the graduates of Brigham Young University—disciples of Jesus Christ who are driven by love for God and His children and who are prepared to serve and lead. This preparation demands a unique university model: at BYU, bel...
Compliance Ranges Comparison

Vanderbilt University







Brigham Young University






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

Vanderbilt University

Brigham Young 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.