Comparison Overview
Phinity Risk Solutions

Phinity Risk Solutions
Unit 1, The chq Building, Custom House Quay , Dublin, D01, D01, IE
Last Update: 02/02/2026
PHINITY RISK SOLUTIONS INNOVATE, SO THAT YOU CAN MAKE MORE INFORMED DECISIONS The Phinity Risk Solutions platform integrates into your risk and compliance processes to help you decrease your risk exposure. Boost your risk management capability and manage your organisat...

Snowflake
The Cloud, US
Last Update: 06/10/2026
**Snowflake is proud to be the Official Data Collaboration Provider for LA28 and Team USA.** Snowflake delivers the AI Data Cloud — a global network where thousands of organizations mobilize data with near-unlimited scale, concurrency, and performance. Inside the AI Da...
Compliance Ranges Comparison

Phinity Risk Solutions







Snowflake






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
No incidents recorded for Phinity Risk Solutions in 2026.
Incidents vs Software Development Industry Avg (This Year)
Snowflake has 1174.51% more incidents than the average of all companies with at least one recorded incident.
Incident History - Phinity Risk Solutions (X = Date, Y = Severity)
Phinity Risk Solutions cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Snowflake (X = Date, Y = Severity)
Snowflake cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Phinity Risk Solutions

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