Comparison Overview
Guide Dogs for the Blind

Guide Dogs for the Blind
350 Los Ranchitos Road, None, San Rafael, CA, US, 94903
Last Update: 20/03/2026
At Guide Dogs for the Blind (GDB), we believe that everyone deserves to move through the world safely and confidently—to live the life they want to live. Our passionate community employs innovative practices to create life-changing partnerships. And, we advocate for the...

Care.com
2801 N Central Expy, 11th Floor, Dallas, Texas, US, 75204
Last Update: 14/09/2026
Care.com is where families go to find care and where caregivers go to find meaningful work. Since 2007, over 45 million people have turned to Care.com—across child care, senior care, adult care, pet care and housekeeping. We’re here to make care simpler, smarter and mor...
Compliance Ranges Comparison

Guide Dogs for the Blind







Care.com






Benchmark & Cyber Underwriting Signals
Incidents vs Consumer Services Industry Avg (This Year)
No incidents recorded for Guide Dogs for the Blind in 2026.
Incidents vs Consumer Services Industry Avg (This Year)
No incidents recorded for Care.com in 2026.
Incident History - Guide Dogs for the Blind (X = Date, Y = Severity)
Guide Dogs for the Blind cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Care.com (X = Date, Y = Severity)
Care.com cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Guide Dogs for the Blind

Care.com
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.