Comparison Overview
Uranium

Uranium
N/A
Last Update: 01/04/2026
In the current DeFi world, the same problem is encountered by many AMMs : the token value collapses, tends to 0, and the use of DEX decreases before it stops completely. Many strategies have been attempted to avoid this pitfall (the Goose layered farming, exotic burnin...

e&
Abu Dhabi, Abu Dhabi, AE
Last Update: 01/04/2026
We're a global technology group focused on innovation and collaboration to create a better future for all. Since 1976, we've been pioneering new technologies and expanding our reach to more people and places. Today, we provide services to over 163 million customers acro...
Compliance Ranges Comparison

Uranium







e&






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
Uranium has 38.65% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for e& in 2026.
Incident History - Uranium (X = Date, Y = Severity)
Uranium cyber incidents detection timeline including parent company and subsidiaries.
Incident History - e& (X = Date, Y = Severity)
e& cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Uranium

e&
FAQ
Latest Global CVEs
Use after free in Aura in Google Chrome prior to 150.0.7871.128 allowed a local attacker to potentially exploit heap corruption via a malicious file. (Chromium security severity: High)
Use after free in Ozone in Google Chrome on Linux prior to 150.0.7871.128 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
Out of bounds read and write in V8 in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Use after free in Cast in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Use after free in Network in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)