Comparison Overview
pascom GmbH

pascom GmbH
Berger Straße 42, Deggendorf, 94469, DE
Last Update: 29/03/2026
Founded in 1997, pascom are the PASCOM ONE Cloud Telephony solution for business. With pascom as the heart of their communications, businesses have a centralised, intelligent hub giving them total control over their organisation’s communications – no matter how divers...

TIM
Via Gaetano Negri, 1, Milano, 20123, IT
Last Update: 08/09/2026
We are driving the digital transition of Italy and Brazil with innovative technologies and services because we want to contribute to accelerating the sustainable growth of the economy and society by bringing value and prosperity to people, companies and institutions. W...
Compliance Ranges Comparison

pascom GmbH







TIM






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for pascom GmbH in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for TIM in 2026.
Incident History - pascom GmbH (X = Date, Y = Severity)
pascom GmbH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - TIM (X = Date, Y = Severity)
TIM cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

pascom GmbH

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