Comparison Overview
Michigan Department of Licensing and Regulatory Affairs

Michigan Department of Licensing and Regulatory Affairs
611 W Ottawa St, Lansing, 48933, US
Last Update: 29/03/2026
The Michigan Department of Licensing and Regulatory Affairs (LARA) supports business growth and job creation while safeguarding Michigan's citizens through a simple, fair, efficient and transparent regulatory structure. For more information about the LARA, please visit ...

City of Cape Town
12 Hertzog Blvd, Cape Town, Western Cape, ZA, 8001
Last Update: 02/04/2026
Cape Town, or the Mother City, is South Africa’s oldest city, its second-most populous and the legislative capital. It is made up of a diverse population, a rich history, world-famous tourist attractions and an exciting calendar of international and local events. More ...
Compliance Ranges Comparison

Michigan Department of Licensing and Regulatory Affairs







City of Cape Town






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Michigan Department of Licensing and Regulatory Affairs in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for City of Cape Town in 2026.
Incident History - Michigan Department of Licensing and Regulatory Affairs (X = Date, Y = Severity)
Michigan Department of Licensing and Regulatory Affairs cyber incidents detection timeline including parent company and subsidiaries.
Incident History - City of Cape Town (X = Date, Y = Severity)
City of Cape Town cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Michigan Department of Licensing and Regulatory Affairs

City of Cape Town
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.