Comparison Overview
Axios HQ

Axios HQ
3100 Clarendon Blvd, Suite 1300, Arlington, Virginia, US, 22201
Last Update: 21/04/2026
Axios HQ is the first internal communications management platform to equip organizations with the tools, data, and best practices to be world-class communicators.

PedidosYa
La Cumparsita 1475, 11200 Montevideo, Departamento de Montevideo, Montevideo, Montevideo, UY, 11200
Last Update: 02/04/2026
We’re the delivery market leader in Latin America. Our platform connects over 77.000 restaurants, supermarkets, pharmacies and stores with millions of users. Nowadays we operate in more than 500 cities in Latinamerica. And we are now over 3.400 employees. PedidosYa is ...
Compliance Ranges Comparison

Axios HQ







PedidosYa






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

Axios HQ

PedidosYa
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.