Comparison Overview
VASS LATAM

VASS LATAM
Carrera 15 Nro. 98-42. Oficina 306, Edificio Office Point, Bogotá D.C., CO
Last Update: 02/04/2026
VASS is a leading digital solutions company, with presence in 26 countries across Europe, America and Asia. We help large companies in their digital transformation process, developing and executing the most innovative and scalable projects, from strategy to operations....

Persistent Systems
Bhageerath, 402 E, Senapati Bapat Road, Pune, Maharashtra, IN, 411016
Last Update: 02/04/2026
We are an AI-led, platform-driven Digital Engineering and Enterprise Modernization partner, combining deep technical expertise and industry experience to help our clients anticipate what’s next. Our offerings and proven solutions create a unique competitive advantage fo...
Compliance Ranges Comparison

VASS LATAM







Persistent Systems






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for VASS LATAM in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Persistent Systems in 2026.
Incident History - VASS LATAM (X = Date, Y = Severity)
VASS LATAM cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Persistent Systems (X = Date, Y = Severity)
Persistent Systems cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

VASS LATAM

Persistent Systems
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.