Comparison Overview
Acorn

Acorn
Croeselaan 18, Utrecht, 3521 CB, NL
Last Update: 06/03/2026
Acorn is on a mission to empower smallholder farmers globally. We support them as they transition to sustainable agroforestry practices and measure the resulting biomass increase, issuing carbon credits accordingly. These we then sell to responsible corporates, with 80%...

SUEZ
La Défense, Paris, 92040, FR
Last Update: 13/09/2026
We provide essential services in the water and waste sectors to preserve resources and improve quality of life wherever we operate. As a global player for over 160 years, we support public and private actors with resilient and innovative solutions. With a presence in ...
Compliance Ranges Comparison

Acorn







SUEZ






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

Acorn

SUEZ
FAQ
Latest Global CVEs
Authorization Bypass Through User-Controlled Key vulnerability in Ultimate Member Ultimate Member ultimate-member allows Privilege Escalation.This issue affects Ultimate Member: from n/a through 2.13.1.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Unlimited Elements Unlimited Elements For Elementor (Free Widgets, Addons, Templates) unlimited-elements-for-elementor allows Reflected XSS.This issue affects Unlimited Elements For Elementor (Free Widgets, Addons, Templates): from n/a through 2.0.20.
Improper Validation of Specified Quantity in Input vulnerability in Themeum Kirki kirki allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Kirki: from n/a through 6.3.1.
OpenAM before 16.1.3 contains a server-side request forgery vulnerability that allows attackers able to register or modify OAuth 2.0 clients to make OpenAM fetch internal resources via an unvalidated jwks_uri. Attackers can trigger unauthenticated fetches through client-authentication and ID-token validation to probe internal hosts, metadata endpoints or local files, or exhaust request threads for denial of service.
OpenAM before 16.1.3 contains an improper authorization vulnerability that allows delegated administrators to destroy sessions outside their realms because realm checks use the requester's realm. Authenticated accounts holding the iplanet-am-session-destroy-sessions attribute can supply a target session identifier or handle to forcibly log out users in any realm.