Comparison Overview
Georgia-Pacific Packaging & Cellulose

Georgia-Pacific Packaging & Cellulose
Atlanta, US
Last Update: 09/03/2026
Georgia-Pacific Packaging is a global leader in customer-focused, fiber-based solutions. What does that mean to you? Fresh produce is safely delivered from the field to your table, your online order is protected through the supply chain and disposable cups serve up your...

RGE
80 Raffles Place, #50-01 , Singapore, Singapore, SG, 048624
Last Update: 28/03/2026
Headquartered in Singapore, RGE is a global group of companies in the bio-based resources and energy sectors, serving over 100 markets worldwide. With more than US$40 billion in assets and a workforce of 80,000 employees, our operations span across Indonesia, China, Bra...
Compliance Ranges Comparison

Georgia-Pacific Packaging & Cellulose







RGE






Benchmark & Cyber Underwriting Signals
Incidents vs Paper and Forest Product Manufacturing Industry Avg (This Year)
No incidents recorded for Georgia-Pacific Packaging & Cellulose in 2026.
Incidents vs Paper and Forest Product Manufacturing Industry Avg (This Year)
No incidents recorded for RGE in 2026.
Incident History - Georgia-Pacific Packaging & Cellulose (X = Date, Y = Severity)
Georgia-Pacific Packaging & Cellulose cyber incidents detection timeline including parent company and subsidiaries.
Incident History - RGE (X = Date, Y = Severity)
RGE cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Georgia-Pacific Packaging & Cellulose

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