Comparison Overview
OCP Portugal

OCP Portugal
R. do Barreiro 235 , Maia, 4470-573 , PT
Last Update: 24/04/2026
A OCP Portugal é uma empresa de distribuição farmacêutica de serviço completo com dimensão nacional e assume-se como um dos principais players no mercado de distribuição de produtos farmacêuticos a nível nacional. Sediados na Maia, atualmente contamos com cerca de 290 c...

Wesco
225 W Station Square Dr, Pittsburgh, Pennsylvania, US, 15219
Last Update: 12/08/2026
At Wesco, we believe life should run smoothly. As a leading provider of business-to-business distribution, logistics services and supply chain solutions, we create a world that you can depend on. Harnessing 100 years of ingenuity and expertise, we increase profitability...
Compliance Ranges Comparison

OCP Portugal







Wesco






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

OCP Portugal

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