Comparison Overview
Privy Council Office

Privy Council Office
Ottawa, K1A 0A3, CA
Last Update: 16/08/2026
The Privy Council Office (PCO) supports the Prime Minister and Cabinet. Led by the Clerk of the Privy Council, the department helps the government in implementing its vision, goals and decisions in a timely manner

State of Michigan
State Capitol, Lansing, Michigan, US, 48913
Last Update: 01/04/2026
Every day the contributions and achievements of State of Michigan employees have a direct impact on over 10 million Michiganders across the state. If you're looking for a fulfilling career in state government that can make a real difference in the lives of others, you c...
Compliance Ranges Comparison

Privy Council Office







State of Michigan






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

Privy Council Office

State of Michigan
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.