Comparison Overview
Vector Disease Control International (VDCI)

Vector Disease Control International (VDCI)
1320 Brookwood Drive, Little Rock, AR, 72202, US
Last Update: 28/11/2025
Vector Disease Control International (VDCI) partners with municipalities, city and state governments and commercial properties to provide mosquito management services to communities in more than 20 states and internationally. VDCI strives to improve the quality of life ...

Dalkia
204 rue Sadi Carnot , Saint-André-Lez-Lille, 59350, FR
Last Update: 13/09/2026
Dalkia : ensemble, relevons le défi climatique ! Depuis 85 ans, Dalkia, filiale du groupe EDF et leader dans les services énergétiques, investit et développe les énergies renouvelables et de récupération et accompagne ses clients dans la durée pour les aider à faire des...
Compliance Ranges Comparison

Vector Disease Control International (VDCI)







Dalkia






Benchmark & Cyber Underwriting Signals
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for Vector Disease Control International (VDCI) in 2026.
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for Dalkia in 2026.
Incident History - Vector Disease Control International (VDCI) (X = Date, Y = Severity)
Vector Disease Control International (VDCI) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dalkia (X = Date, Y = Severity)
Dalkia cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Vector Disease Control International (VDCI)

Dalkia
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.