Comparison Overview
Databricks for Industrials

Databricks for Industrials
N/A
Last Update: 27/08/2026
Databricks for Industrials is the official Databricks channel for manufacturing, transportation, and energy. More than 20,000 organizations worldwide rely on Databricks to build and scale data and AI apps, analytics and agents. This page focuses on what that looks like...

Prysmian
Via Chiese 6, Milan, Italy, IT, 20126
Last Update: 20/09/2026
Prysmian is a global cabling solutions provider leading the energy transition and digital transformation. By leveraging its wide geographical footprint and extensive product range, its track record of technological leadership and innovation, and a strong customer base, ...
Compliance Ranges Comparison

Databricks for Industrials







Prysmian






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

Databricks for Industrials

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