Comparison Overview
Purple Mountain Observatory, CAS

Purple Mountain Observatory, CAS
No.10 Yuanhua Road, Nanjing, JS, 210034, CN
Last Update: 22/03/2026
The Purple Mountain Observatory (PMO) evolved from the former Institute of Astronomy, which was established in 1928 as one of the first eight institutes of the Academia Sinica. In 1934, the institute completed the construction of the observatory at Purple Mountain in Na...

Utrecht University
Heidelberglaan 6, Utrecht, Utrecht, 3512, NL
Last Update: 02/04/2026
At Utrecht University (UU), we are working towards a better world. We do this by researching complex issues beyond the borders of disciplines. We put thinkers in contact with doers, so new insights can be applied. We give students the space to develop themselves. In so ...
Compliance Ranges Comparison

Purple Mountain Observatory, CAS







Utrecht University






Benchmark & Cyber Underwriting Signals
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for Purple Mountain Observatory, CAS in 2026.
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for Utrecht University in 2026.
Incident History - Purple Mountain Observatory, CAS (X = Date, Y = Severity)
Purple Mountain Observatory, CAS cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Utrecht University (X = Date, Y = Severity)
Utrecht University cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Purple Mountain Observatory, CAS

Utrecht 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.