Comparison Overview
Famly

Famly
Købmagergade 19, Copenhagen K, 1150, DK
Last Update: 13/12/2025
Great early childhood happens together. But the world seems to forget that - too many nurturing adults are working in isolation. Isolation from families and other caregivers. From key information. From exciting and innovative partners, experts, or centers of excellence....

Pitney Bowes
27 Waterview Dr, Shelton, 06484, US
Last Update: 07/10/2026
Pitney Bowes is a technology-driven company that provides digital shipping solutions, mailing innovation, and financial services to clients around the world – including more than 90 percent of the Fortune 500. Small businesses to large enterprises, and government entiti...
Compliance Ranges Comparison

Famly







Pitney Bowes






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

Famly

Pitney Bowes
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.