Pi-hole
Last Update: 2026-01-18
Between 700 and 749
Network-Wide Ad Blocking
NAICS: 5112
NAICS Definition: Software Publishers
Employees: 2
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
1
Comparison Overview
Pi-hole
VS
Booking.com
Booking.com
Last Update: 2026-01-18
Between 700 and 749
A career at Booking.com is all about the journey, helping you explore new challenges in a place where you can be your best self. With plenty of exciting twists, turns and opportunities along the way. We’ve always been pioneers, on a mission to shape the future of travel through cutting edge technology, to make it easier for everyone to enjoy amazing experiences wherever they go. Under a desert sky, or in the heart of a bustling city. Discovering the perfect hideaway, or the perfect paella. When you join us, you’ll be part of a community where taking a different path and trying something new is celebrated and supported. And where making a difference counts. We’re determined to make the world of travel more sustainable, more accessible, and more inclusive, to create a positive impact on a global scale. That’s why we’re always looking for people who search for better solutions, the ones eager to stray off the beaten path to find new ways of doing things. Because at Booking.com it’s more than a job, it’s a journey we’re on together.
NAICS: 5112
NAICS Definition: Software Publishers
Employees: 16,202
Subsidiaries: 11
12-month incidents
0
Known data breaches
1
Attack type number
2
Compliance Badges Comparison
Security & Compliance Standards Overview
Pi-hole
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
Booking.com
ISO 27001
Not verified
SOC2 Type 1
Not verified
SOC2 Type 2
Not verified
GDPR
Not verified
PCI DSS
Not verified
HIPAA
Not verified
Compliance Summary
Pi-hole
100%
Compliance Rate
0/4 Standards Verified
Booking.com
0%
Compliance Rate
0/4 Standards Verified
Benchmark & Cyber Underwriting Signals
Incidents vs Software Development Industry Average (This Year)
No incidents recorded for Pi-hole in 2026.
Incidents vs Software Development Industry Average (This Year)
No incidents recorded for Booking.com in 2026.
Incident History — Pi-hole (X = Date, Y = Severity)
Pi-hole cyber incidents detection timeline including parent company and subsidiaries
Incident History — Booking.com (X = Date, Y = Severity)
Booking.com cyber incidents detection timeline including parent company and subsidiaries
Notable Incidents
Last 3 Security & Risk Events by Company
Pi-hole
Incidents
Booking.com
Incidents
Date Detected: 6/2025
Type:Cyber Attack
Attack Vector: Mass-phishing, Infostealer trojans
Motivation: Financial gain
Blog: Blog
Date Detected: 4/2025
Type:Cyber Attack
Attack Vector: compromised email accounts, phishing links, fake reCAPTCHA challenge, malware download (PureRAT), personalized WhatsApp messages, fake Booking/Expedia websites
Motivation: financial gain, data theft, fraudulent transactions
Blog: Blog
Date Detected: 2/2025
Type:Cyber Attack
Attack Vector: malicious domain registration, social engineering, phishing emails/websites
Motivation: financial gain, theft of payment details
Blog: Blog
FAQ
Pi-hole company demonstrates a stronger AI Cybersecurity Score compared to Booking.com company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.
Booking.com company has faced a higher number of disclosed cyber incidents historically compared to Pi-hole company.
In the current year, Booking.com company and Pi-hole company have not reported any cyber incidents.
Neither Booking.com company nor Pi-hole company has reported experiencing a ransomware attack publicly.
Booking.com company has disclosed at least one data breach, while Pi-hole company has not reported such incidents publicly.
Booking.com company has reported targeted cyberattacks, while Pi-hole company has not reported such incidents publicly.
Pi-hole company has disclosed at least one vulnerability, while Booking.com company has not reported such incidents publicly.
Neither Pi-hole nor Booking.com holds any compliance certifications.
Neither company holds any compliance certifications.
Booking.com company has more subsidiaries worldwide compared to Pi-hole company.
Booking.com company employs more people globally than Pi-hole company, reflecting its scale as a Software Development.
Neither Pi-hole nor Booking.com holds SOC 2 Type 1 certification.
Neither Pi-hole nor Booking.com holds SOC 2 Type 2 certification.
Neither Pi-hole nor Booking.com holds ISO 27001 certification.
Neither Pi-hole nor Booking.com holds PCI DSS certification.
Neither Pi-hole nor Booking.com holds HIPAA certification.
Neither Pi-hole nor Booking.com holds GDPR certification.
Latest Global CVEs (Not Company-Specific)
Description
SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g., execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.
Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description
Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Description
Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).
Risk Information
cvss3
Base: 8.1
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
Description
Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Description
Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
