Comparison Overview
Georgia-Pacific LLC
Georgia-Pacific LLC
133 Peachtree St NE, Atlanta, GA, US, 30303
Last Update: 20/12/2025
Georgia-Pacific and its subsidiaries are among the world’s leading manufacturers and marketers of bath tissue, paper towels and napkins, tableware, paper-based packaging, cellulose, specialty fibers and building products. The company operates more than 150 facilities an...
International Paper
6400 Poplar Ave, Memphis, 38197, US
Last Update: 05/04/2026
International Paper (NYSE: IP; LSE: IPC) is the global leader in sustainable packaging solutions. With company headquarters in Memphis, Tennessee, USA, and EMEA (Europe, Middle East and Africa) headquarters in London, UK, we employ more than 65,000 team members and serv...
Compliance Ranges Comparison
Georgia-Pacific LLC
International Paper
Benchmark & Cyber Underwriting Signals
Incidents vs Paper and Forest Product Manufacturing Industry Avg (This Year)
No incidents recorded for Georgia-Pacific LLC in 2026.
Incidents vs Paper and Forest Product Manufacturing Industry Avg (This Year)
No incidents recorded for International Paper in 2026.
Incident History - Georgia-Pacific LLC (X = Date, Y = Severity)
Georgia-Pacific LLC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - International Paper (X = Date, Y = Severity)
International Paper cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Georgia-Pacific LLC
International Paper
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.