Comparison Overview
Polioles

Polioles
Fernando Montes de Oca 71, Cuauhtemoc, CDMX, 06140, MX
Last Update: 06/02/2026
En Polioles generamos soluciones integrales para nuestros clientes a través de la innovación y la responsabilidad con el entorno. La seguridad es nuestra cultura de trabajo y juntos somos un equipo de alto desempeño con enfoque a la excelencia operativa. En Polioles dec...

Asahi Kasei
1-1-2 Yurakucho, Chiyoda-ku, Tokyo, 100-0006, JP
Last Update: 15/09/2026
🏢 About Asahi Kasei The Asahi Kasei Group contributes to life and living for people around the world. Since its foundation in 1922 with ammonia and cellulose fiber business, Asahi Kasei has consistently grown through the proactive transformation of its business portfol...
Compliance Ranges Comparison

Polioles







Asahi Kasei






Benchmark & Cyber Underwriting Signals
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Polioles in 2026.
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Asahi Kasei in 2026.
Incident History - Polioles (X = Date, Y = Severity)
Polioles cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Asahi Kasei (X = Date, Y = Severity)
Asahi Kasei cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Polioles

Asahi Kasei
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.