Comparison Overview
Lyreco Finland Oy

Lyreco Finland Oy
Väinö Tannerin tie, Vantaa, 01510, FI
Last Update: 24/01/2026
Lyreco Finland – Kumppanisi sujuvampaan työpäivään Lyreco Finland Oy on Suomen johtava työpaikkatarviketoimittaja, joka palvelee yrityksiä valtakunnallisesti. Vantaan pääkonttoristamme ja logistiikkakeskuksestamme käsin lähes 200 asiantuntijaamme takaavat sujuvan palve...

Staples
500 Staples Drive, Framingham, 01702, US
Last Update: 01/04/2026
For nearly 40 years, Staples has been a trusted leader in delivering end-to-end workplace solutions for consumers and businesses of all sizes across a broad range of industries. The company provides a comprehensive portfolio of products, strategic solutions, and service...
Compliance Ranges Comparison

Lyreco Finland Oy







Staples






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Office Equipment Industry Avg (This Year)
No incidents recorded for Lyreco Finland Oy in 2026.
Incidents vs Retail Office Equipment Industry Avg (This Year)
Staples has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Lyreco Finland Oy (X = Date, Y = Severity)
Lyreco Finland Oy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Staples (X = Date, Y = Severity)
Staples cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Lyreco Finland Oy

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