Comparison Overview
Michigan Department of Attorney General

Michigan Department of Attorney General
525 W. Ottawa Street, Lansing, 48909, US
Last Update: 28/03/2026
Official page with helpful information, updates and the latest news from Michigan's Department of Attorney General, led by Attorney General Dana Nessel. Page is managed by department staff and is not a personal page for Attorney General Nessel.

Etat de Vaud
Rue Caroline 4, Lausanne, 1014, CH
Last Update: 31/03/2026
Le canton de Vaud, c’est plus de 800 000 personnes vivant dans plus de 300 communes ! Rejoindre l’Administration cantonale vaudoise, c’est s’engager aux côtés de près de 40’000 personnes unies dans un même but : servir la population. Pourquoi nous suivre ? Dédiez vot...
Compliance Ranges Comparison

Michigan Department of Attorney General







Etat de Vaud






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Michigan Department of Attorney General in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Etat de Vaud in 2026.
Incident History - Michigan Department of Attorney General (X = Date, Y = Severity)
Michigan Department of Attorney General cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Etat de Vaud (X = Date, Y = Severity)
Etat de Vaud cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Michigan Department of Attorney General

Etat de Vaud
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.