Comparison Overview
Instrument

Instrument
3529 N Williams Ave, Portland, Oregon, 97227, US
Last Update: 05/12/2025
We are a design and technology company helping brands unlock their full potential. We've been bringing brands and people closer together and driving lasting business impact since 2005. Start a project: [email protected] Press & media: [email protected] Eve...

RR Donnelley
227 W Monroe St, Chicago, 60606, US
Last Update: 04/04/2026
RRD provides a complete portfolio of marketing, packaging, print and business services to the world’s most respected brands, including 91% of the Fortune 100. Our proprietary technology, advanced data analytics and established expertise fuel organizational decision-ma...
Compliance Ranges Comparison

Instrument







RR Donnelley






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

Instrument

RR Donnelley
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.