Comparison Overview
AD/01
AD/01
Bulevardul Iancu de Hunedoara, Bucharest, undefined, undefined, RO
Last Update: 03/02/2026
Hi, we’re AD/01 This is our story. Where do you see yourself in 5 years? Are you hidden away making things for the few, who don’t notice the effort? Are you debugging someone else’s legacy code,and realizing your favorite programming language has now become profanit...
Nothing
John Street, London, GB
Last Update: 30/09/2026
Nothing exists to make tech feel exciting again. We’re building a different kind of company, one that puts design, emotion, and human creativity at the heart of everything we do. From the way our products look to how they sound, feel, and function, we care about the de...
Compliance Ranges Comparison
AD/01
Nothing
Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for AD/01 in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
Nothing has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - AD/01 (X = Date, Y = Severity)
AD/01 cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Nothing (X = Date, Y = Severity)
Nothing cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AD/01
Nothing
FAQ
Latest Global CVEs
The web management service in affected RouterOS versions contains an integer underflow in its HTTP request body handling that is reachable before authentication. This can be leveraged by an unauthenticated network attacker to achieve arbitrary code execution as root, or to cause a denial of service, using a single crafted request.
Denuvo Anti-Tamper through 2026-03-04 allows bypass of a hypervisor presence check via CPUID interception (SimpleSvm.sys on AMD; hyperkd.sys and hyperhv.dll on Intel).
PeaZip before 11.3.0, in a non-default configuration, is vulnerable to OS command injection via a filename in an archive because "quotation character already used in the string" is mishandled.
Zilliz Attu before 3.0.0 has a Playground feature that does not require authentication for proxying arbitrary HTTP and HTTPS requests to URLs on the public internet.
The Playground feature of Zilliz Attu before 3.0.0 allows SSRF (proxying of requests to private IP addresses).