Comparison Overview
Infosys BPM

Infosys BPM
Infosys BPM Limited, Plot no 26/3, 26/4, 26/6, Hosur Road, Electronics City, Bengaluru, 560100, IN
Last Update: 09/09/2026
Infosys BPM Ltd., the business process management subsidiary of Infosys Ltd. (NYSE: INFY), was set up in April 2002. Infosys BPM focuses on integrated end-to-end outsourcing and delivers transformational benefits to its clients through reduced costs, ongoing productivit...

Hexaware Technologies
#1, Sector III, Millennium Business Park,, 'A' Block , TTC Industrial Estate, Mahape,, Navi Mumbai, Maharashtra, IN, 400710
Last Update: 17/08/2026
At Hexaware, we're not just a global technology and business process services company; we're a community of 31,600+ Hexawarians dedicated to one singular purpose: creating smiles through the power of great people and technology. With a presence in 58 offices across 28 c...
Compliance Ranges Comparison

Infosys BPM







Hexaware Technologies






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Infosys BPM in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Hexaware Technologies has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Infosys BPM (X = Date, Y = Severity)
Infosys BPM cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hexaware Technologies (X = Date, Y = Severity)
Hexaware Technologies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Infosys BPM

Hexaware Technologies
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.