Comparison Overview
Expensify

Expensify
88 Kearny St, San Francisco, CA, 94104, US
Last Update: 04/04/2026
Expensify helps more than 12 million people around the world track expenses, reimburse employees, manage corporate cards, send invoices, pay bills, and book travel. All in one app. So whether you're working for yourself, running a small business, managing a team, or clo...

Bosch
Robert-Bosch-Platz 1, Gerlingen-Schillerhöhe, 70839, DE
Last Update: 14/09/2026
The Bosch Group is a leading global supplier of technology and services. It employs roughly 417,900 associates worldwide (as of December 31, 2024). According to preliminary figures, the company generated sales of 90.5 billion euros in 2024. Its operations are divided in...
Compliance Ranges Comparison

Expensify







Bosch






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

Expensify

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