Comparison Overview
Corning Optical Communications

Corning Optical Communications
4200 Corning Pl, Charlotte, NC, 28216, US
Last Update: 18/03/2026
Corning Optical Communications is a leading manufacturer of fiber optic communications system solutions for voice, data and video network applications worldwide.

Telkom Indonesia
Jalan Jenderal Gatot Subroto Kav. 52, Jakarta Selatan, 40264, ID
Last Update: 13/09/2026
PT Telkom Indonesia (Persero) Tbk (Telkom) is a state-owned information and communications technology enterprise and telecommunications network in Indonesia. The Government of Indonesia is the majority shareholder with 52.09 percent shares while the remaining 47.91 perc...
Compliance Ranges Comparison

Corning Optical Communications







Telkom Indonesia






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Corning Optical Communications in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Telkom Indonesia in 2026.
Incident History - Corning Optical Communications (X = Date, Y = Severity)
Corning Optical Communications cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Telkom Indonesia (X = Date, Y = Severity)
Telkom Indonesia cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Corning Optical Communications

Telkom Indonesia
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.