Comparison Overview
CR&R Incorporated

CR&R Incorporated
11292 Western Avenue, Stanton, 90680, US
Last Update: 01/04/2026
CR&R Incorporated is one of Southern California's most innovative and successful environmental recycling collection companies, serving more than 3 million people and over 25,000 businesses throughout Orange, Los Angeles, San Bernardino, Imperial and Riverside counties.

Republic Services
18500 N. Allied Way, Phoenix, 85054, US
Last Update: 13/09/2026
Republic Services provides the most complete set of recycling, waste and environmental solutions from a single-source provider. We partner with customers to help them achieve their sustainability goals, driving both environmental and economic sustainability. We offer ad...
Compliance Ranges Comparison

CR&R Incorporated







Republic Services






Benchmark & Cyber Underwriting Signals
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for CR&R Incorporated in 2026.
Incidents vs Environmental Services Industry Avg (This Year)
No incidents recorded for Republic Services in 2026.
Incident History - CR&R Incorporated (X = Date, Y = Severity)
CR&R Incorporated cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Republic Services (X = Date, Y = Severity)
Republic Services cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

CR&R Incorporated

Republic Services
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.