Comparison Overview
Sany India

Sany India
Chakan Industrial Area, Phase 3, Pune, 410501, IN
Last Update: 19/04/2026
SANY Heavy Industry India Pvt Ltd (SANY India) is a wholly owned subsidiary of SANY Heavy Industry Co Ltd (SANY Heavy Industry), China, with a manufacturing facility Chakan Pune and a leader in construction equipment industry. SANY India was established in December 200...

John Deere
Moline, 61265, US
Last Update: 24/09/2026
It doesn’t matter if you’ve never driven a tractor, mowed a lawn, or operated a dozer. With John Deere’s role in helping produce food, fiber, fuel, and infrastructure, we work for every single person on the planet. It all started nearly 200 years ago with a steel plow...
Compliance Ranges Comparison

Sany India







John Deere






Benchmark & Cyber Underwriting Signals
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Sany India in 2026.
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for John Deere in 2026.
Incident History - Sany India (X = Date, Y = Severity)
Sany India cyber incidents detection timeline including parent company and subsidiaries.
Incident History - John Deere (X = Date, Y = Severity)
John Deere cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sany India

John Deere
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.