Comparison Overview
Dragontail Systems

Dragontail Systems
673 Bourke Street, Melbourne, undefined, undefined, undefined, AU
Last Update: 08/03/2026
Dragontail Systems is a global leading B2B company, that provides a revolutionary software solution to optimize and streamline the food preparation and dispatch, mainly to the QSR (Quick Service Restaurant) industry. We are proud to be part of Yum! Brands, a company w...

Tieto
N/A
Last Update: 19/09/2026
Tieto provides customers across different industries with mission-critical solutions through its specialized software businesses Tieto Caretech, Tieto Banktech and Tieto Indtech as well as Tieto Tech Consulting business. The company's around 13 000 talented vertical sof...
Compliance Ranges Comparison

Dragontail Systems







Tieto






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Dragontail Systems in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Tieto in 2026.
Incident History - Dragontail Systems (X = Date, Y = Severity)
Dragontail Systems cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tieto (X = Date, Y = Severity)
Tieto cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Dragontail Systems

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