Comparison Overview
Deutsche Telekom Digital Labs

Deutsche Telekom Digital Labs
DLF Cyber City, Gurgaon, 122002, IN
Last Update: 01/01/2026
Welcome to Deutsche Telekom Digital Labs (DTDL) – where tech meets purpose. We’re the innovation engine behind Deutsche Telekom, building seamless digital experiences that simplify everyday life. Whether it’s streaming, shopping, chatting, paying, or asking your digita...

Times Internet
391, Udyog Vihar Phase III, Gurgaon , Haryana, IN, 122002
Last Update: 25/09/2026
At Times Internet, we create premium digital products that simplify and enhance the lives of millions. As India’s largest digital products company, we have a significant presence across a wide range of categories, including News, Sports, Fintech, and Enterprise solution...
Compliance Ranges Comparison

Deutsche Telekom Digital Labs







Times Internet






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

Deutsche Telekom Digital Labs

Times Internet
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.