Comparison Overview
U.S. Consulate General Mumbai

U.S. Consulate General Mumbai
C49, G Block Rd, G Block BKC, Bandra Kurla Complex, Bandra East, Mumbai, Mumbai, 400051, IN
Last Update: 05/01/2026
Welcome to the official LinkedIn page of the Consulate General of the United States in Mumbai, a resource for you to connect with us, learn about #USIndia economic partnerships, engage with our visiting experts on wide-ranging topics such as entrepreneurship, innovation...

Workingfor.be
Simon Bolivarlaan 30, Brussels, 1000, BE
Last Update: 01/04/2026
Workingfor.be is the job platform of the federal administration. Here, you will find a wide variety of jobs in different fields of profession. Every day thousands of our employees help build tomorrow's society. When you choose the federal administration, you choos...
Compliance Ranges Comparison

U.S. Consulate General Mumbai







Workingfor.be






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for U.S. Consulate General Mumbai in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Workingfor.be in 2026.
Incident History - U.S. Consulate General Mumbai (X = Date, Y = Severity)
U.S. Consulate General Mumbai cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Workingfor.be (X = Date, Y = Severity)
Workingfor.be cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

U.S. Consulate General Mumbai

Workingfor.be
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.