Comparison Overview
CRIF Poland

CRIF Poland
ulica Lublańska 34, Kraków, PL
Last Update: 06/03/2026
CRIF's mission is to improve the quality of economic life via use of the advanced technologies that enable our Partners to make efficient business decisions. The unique nature of the CRIF services is determined by high level of automation of decision-making processes as...

Zoom
55 Almaden Blvd., 6th Floor, San Jose, CA 95113, San Jose, 95113, US
Last Update: 14/10/2026
Bring teams together, reimagine workspaces, engage new audiences, and delight your customers –– all on the Zoom AI-first work platform you know and love. 💙 Zoomies help people stay connected so they can get more done together. We set out on a mission to make video com...
Compliance Ranges Comparison

CRIF Poland







Zoom






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for CRIF Poland in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Zoom has 586.27% more incidents than the average of all companies with at least one recorded incident.
Incident History - CRIF Poland (X = Date, Y = Severity)
CRIF Poland cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Zoom (X = Date, Y = Severity)
Zoom cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

CRIF Poland

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