Comparison Overview
National Nuclear Security Administration (NNSA)

National Nuclear Security Administration (NNSA)
1000 Independence Avenue SW, Washington, 20585, US
Last Update: 01/04/2026
Established by Congress in 2000, NNSA is a semi-autonomous agency within the U.S. Department of Energy that protects our nation by designing and delivering a safe, secure, reliable, and effective U.S. nuclear stockpile; forging solutions that enable global security and ...

City of Amsterdam
Postbus 202, Amsterdam, 1000 AE, NL
Last Update: 14/09/2026
Working for Amsterdam means working for the most beautiful city in the world. Think of its rich history, the role Amsterdam plays internationally, and events such as Sail, Gay Pride and King’s Day. Of course everybody wants to visit Amsterdam, or work or live here. As ...
Compliance Ranges Comparison

National Nuclear Security Administration (NNSA)







City of Amsterdam






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for National Nuclear Security Administration (NNSA) in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for City of Amsterdam in 2026.
Incident History - National Nuclear Security Administration (NNSA) (X = Date, Y = Severity)
National Nuclear Security Administration (NNSA) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - City of Amsterdam (X = Date, Y = Severity)
City of Amsterdam cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

National Nuclear Security Administration (NNSA)

City of Amsterdam
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.