Comparison Overview
OpenSearch Project

OpenSearch Project
San Francisco, US
Last Update: 29/05/2026
OpenSearch is the trusted vendor-neutral open source platform for AI-powered search, analytics, observability, and vector database solutions. Built for scalability, performance, and extensibility, developers and enterprises rely on OpenSearch to securely manage workload...

Workday
6110 Stoneridge Mall Rd, Pleasanton, 94588, US
Last Update: 12/09/2026
By unifying HR and Finance on an open, trusted platform powered by AI, Workday delivers high-impact outcomes our customers can count on. At the heart of our platform is Sana from Workday—the superintelligence that puts AI agents to work for you and your people. Welcome ...
Compliance Ranges Comparison

OpenSearch Project







Workday






Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Avg (This Year)
OpenSearch Project has 185.71% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Software Development Industry Avg (This Year)
Workday has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - OpenSearch Project (X = Date, Y = Severity)
OpenSearch Project cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Workday (X = Date, Y = Severity)
Workday cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

OpenSearch Project

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