Comparison Overview
Office of the Special Envoy for Critical and Emerging Technology

Office of the Special Envoy for Critical and Emerging Technology
2201 C Street NW, Washington, 20520, US
Last Update: 04/04/2026
The Office of the Special Envoy for Critical and Emerging Technology (S/TECH) is the U.S. Department of State's focal point for strategic competition; for cooperation with allies and partners on critical and emerging technologies; and leads the planning for integrated i...

Västra Götalandsregionen
Västra Götalandsregionen, Vänersborg, 462 80, SE
Last Update: 04/04/2026
Region Västra Götaland is governed by democratically elected politicians and with just over 50,000 employees is one of Sweden’s biggest employers. It is tasked with offering good healthcare and dental care and providing the prerequisites for good public health, a ric...
Compliance Ranges Comparison

Office of the Special Envoy for Critical and Emerging Technology







Västra Götalandsregionen






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Office of the Special Envoy for Critical and Emerging Technology in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Västra Götalandsregionen in 2026.
Incident History - Office of the Special Envoy for Critical and Emerging Technology (X = Date, Y = Severity)
Office of the Special Envoy for Critical and Emerging Technology cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Västra Götalandsregionen (X = Date, Y = Severity)
Västra Götalandsregionen cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Office of the Special Envoy for Critical and Emerging Technology

Västra Götalandsregionen
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.