Booking.com: Privacy & Security Findings

report - rfi-irfos
Skip to content

Permanent Disclosure Ledger

The discipline, demonstrated

On behalf of our research partners, we investigate publicly distributed Android and iOS apps: we decompile them, follow their code and data flows, and trace every connection to the servers it reaches. Hundreds of agents work through each app and join the technical evidence into one picture, which our specialists then review and verify.

387+
Android/iOS apps audited
Every app is decompiled at source-code level, not just scanned from outside.
1.04M+
Smali classes read
The full shipped code we have actually read, not an estimate.
262+
Critical findings recorded
Confirmed findings copied to regulators, not theoretical risks.
970+
Weak points found
Third-party tracking we have provably found inside the binary.
567+
Endpoints investigated
Real servers and countries where data actually flows.
132+
SDK instances mapped
Reusable libraries correlated across the entire corpus.
1 of 387 entries · sorted by elapsed ↓
Showing the report for Booking.com.
OrganisationNotifiedStatusSevIntel (click to expand)StatutesResolvedDisclosureElapsedReport
Booking.com
NASDAQ
2026-06-20
91d ago
Waiting
Critical
Booking.com's app asks for microphone access even though nothing in its code ever uses it, so a live mic permission sits on hundreds of millions of phones, including through the night in hotel rooms. The EU version of the app also bundles a Chinese messaging SDK that Beijing's National Intelligence Law can compel to hand data to state authorities, and none of the payment traffic, covering Braintree, PayPal and Venmo, is protected against interception.
com.booking v32.7.102. 3C 4H. RECORD_AUDIO declared globally with no recoverable implementation (no VOIP, no voice search, no AudioRecord/MediaRecorder calls) on a platform in 500M+ users' pockets while they sleep in hotels. WeChat Open Platform SDK (Tencent, 181 classes) in the EU-distributed APK - PRC NSL exposure. Firebase OAuth credentials hardcoded. Zero certificate pinning across payment (Braintree/PayPal/Venmo), booking and WeChat traffic. R1 2026-06-20, FOLLOW-UP 2026-06-28, no reply
click to expand
GDPR Art. 32(1)(b)GDPR Art. 32(1)(a)GDPR Art. 44+3
Yes
Closed
Disclosure
91d 00h 00m 00s
Published
PDF

This ledger is updated in real time as companies respond. Silence is public. Severity is scored primarily by CVSS v4.0, we reserve the right to deviate based on blast radius.