Comparison Overview
McHenry County Conservation District

McHenry County Conservation District
18410 US Highway 14, Woodstock, 60098, US
Last Update: 29/03/2026
McHenry County Conservation District exists to preserve, restore and manage natural areas and open spaces for their intrinsic value and for the benefits to present and future generations. McHenry County Conservation District owns and manages over 25,800 acres of open l...

Region Stockholm
Lindhagensgatan 98, Stockholm, 11218, SE
Last Update: 01/04/2026
Är du beredd att tänka nytt och hitta framtidens lösningar? För vårt framtida uppdrag behöver vi medarbetare med hög kompetens, stort engagemang och som strävar efter ständig förbättring. Vid din sida kan du få engagerade kollegor inom hundratals kvalificerade yrken ...
Compliance Ranges Comparison

McHenry County Conservation District







Region Stockholm






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for McHenry County Conservation District in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Region Stockholm in 2026.
Incident History - McHenry County Conservation District (X = Date, Y = Severity)
McHenry County Conservation District cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Region Stockholm (X = Date, Y = Severity)
Region Stockholm cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

McHenry County Conservation District

Region Stockholm
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.