Risk Report Cybersecurity Hospitality

Hotel cybersecurity risk report 2026

Hotels hold guest identity and payment data, depend on many suppliers and lose revenue quickly when the PMS or check-in goes down. This report brings together public research, confirmed incidents and documented attack campaigns from 2024 to 2026, and sets out the priority control for each risk, for independent hotels and hotel groups.

20 August 2026
14 min read
Updated 9 November 2026
Key takeaways
  • In a VikingCloud survey of North American hotel IT and security leaders, 82% said their hotel was hit by a successful cyberattack in summer 2024
  • IBM put the average hospitality breach at about US$4.03 million in 2025, across the organisations in its study
  • SecurityScorecard found that 52.4% of the breaches it analysed in retail and hospitality involved a third party
  • Booking.com, BWH Hotels and Quest Apartment Hotels each confirmed incidents involving guest or reservation data in 2026
  • The priority controls are mostly basic ones: MFA, supplier access control, segmentation, tested recovery and correct PCI DSS scoping

Scope and method

About this report

This report brings together public research, security vendor statistics, incident disclosures and threat research published between 2024 and 2026. It is not an original survey of the hotel market. Hotel-specific figures are labelled separately from cross-industry indicators, and documented attack campaigns are kept apart from confirmed breaches. Where a conclusion is our own analysis, we say so.

What the research shows

The most cited hotel-specific figures come from Peak Season, Peak Risk, a 2025 VikingCloud survey of IT and security leaders at North American hotels about the summer 2024 season. VikingCloud sells security services and the full report is gated, so read the figures as a picture of the North American market, not a global rate. Respondents reported that:

  • 82% of hotels were hit by a successful cyberattack
  • 58% faced five or more attacks
  • 44% of hotels that were attacked had more than 12 hours of downtime
  • 48% of leaders lacked confidence that staff would recognise AI-generated phishing
82%
of North American hotels hit by a successful attack, summer 2024 (VikingCloud)
US$4.03M
average breach cost for hospitality organisations in IBM's 2025 study
52.4%
of analysed retail and hospitality breaches involved a third party (SecurityScorecard)
44%
of attacked hotels had more than 12 hours of downtime (VikingCloud)

On cost, IBM's Cost of a Data Breach Report 2025 estimated an average of about US$4.03 million per breach for the hospitality organisations in its study, against a global average across all sectors of US$4.44 million. The study covers organisations that had a breach, many of them large, so the figure says little about the likely cost for an individual hotel, especially a small one. It does show how expensive a serious incident can become.

SecurityScorecard's 2025 Global Third-Party Breach Report found that 52.4% of the breaches it analysed in the combined retail and hospitality sector involved a third party, the highest rate of any sector. That is a share of breaches, not a share of hotels affected or a count of supplier outages. It does fit the incidents below, where platforms and providers outside the hotel were part of the story.

How the attacks have changed

Stolen credentials and malware-free intrusions

CrowdStrike's 2026 Global Threat Report found that 82% of the detections it recorded across all industries were malware-free. The figure is not specific to hotels, and malware-free covers more than stolen passwords: it includes attackers using legitimate remote tools and built-in system utilities. The lesson for hotels is the same. An attacker who logs into the PMS, email or a supplier portal with a valid account may never trigger antivirus, so MFA, access reviews and sign-in monitoring do more work than file-based detection.

AI-assisted phishing

In the VikingCloud survey, 48% of hotel IT and security leaders lacked confidence that staff could recognise AI-generated phishing. Attackers can now write convincing booking messages, guest complaints and messages that pretend to come from a manager, in fluent language and in volume. Front-desk and reservations staff handle external messages all day and cannot judge by eye whether each one was written with AI. Verification steps help more: call back on a known number before changing payment details, and never run a "fix" that an email or web page tells you to run.

Ransomware and operational disruption

Ransomware against a hotel hits operations as well as data: reservations, check-in and, in some properties, key-card and door-lock systems. At high occupancy, a long outage costs revenue and guest goodwill before any negotiation starts. Many ransomware groups also steal data and threaten to publish it. Paying does not guarantee that the criminals delete what they took or keep it private, so the hotel has to assess the impact of possible exposure whether or not its systems come back.

The infrastructure that widens the attack surface

Hotels connect the PMS, point-of-sale (POS) terminals, booking engines and channel managers, guest Wi-Fi, in-room devices and supplier systems through a set of networks and integrations. Each category below is a common entry point or a route for an attacker to move between systems.

Point-of-sale terminals
POS terminals in restaurants, bars and spas handle card data, which has made them a long-standing target. PCI DSS sets controls such as vulnerability scanning and, depending on the payment environment and validation method, penetration and segmentation testing. Which requirements apply depends on how the hotel takes payments; our article on PCI DSS for hotels explains the scoping.
Smart room IoT
Smart TVs, digital minibars and room automation add devices to the network. Vendors set them up for guest convenience, firmware updates tend to arrive less often than for corporate IT, and default credentials are sometimes left unchanged.
Third-party suppliers
PMS vendors, booking engines, channel managers, payment providers and IT support firms often have remote access to hotel systems or hold hotel data themselves. That access sits outside the hotel's direct control. Two of the 2026 incidents below, at Booking.com and Quest, involved a platform or provider outside the individual hotel.
Guest Wi-Fi
A guest network that is not properly separated can give anyone who connects a route towards the PMS and back-office systems. Network segmentation prevents this, and in our assessments its absence is a frequent finding.

Confirmed incidents and documented campaigns, 2025 and 2026

The first four cases are incidents the organisations confirmed. The fifth is an attack campaign documented by researchers, with no confirmed breach of a named hotel attributed to it.

Booking.com: unauthorised access to reservation data
April 2026

On 13 April 2026 Booking.com confirmed that it had detected unauthorised access to part of its guests' reservation information. Reported exposed data included names, email addresses, phone numbers and details shared with the accommodation; the company said financial information was not accessed. It reset reservation PINs and warned customers about phishing, but did not say how many people were affected or how the access happened.

The risk for hotels and guests is what follows: real booking details make scam messages asking guests to "re-confirm" a card far more convincing. This is separate from an older case. In 2021 the Dutch Data Protection Authority fined Booking.com €475,000 for reporting a 2019 breach 22 days late; in that breach, criminals obtained extranet login details from staff at 40 hotels in the UAE by phone.

BWH Hotels: reservation data in a web application
October 2025 to April 2026

BWH Hotels, the group behind Best Western, WorldHotels and Sure Hotels, said it found unauthorised activity on 22 April 2026 in a web application holding reservation data, with access reported to go back to 14 October 2025. Exposed data included guest names, contact details, reservation numbers and stay dates; payment card data was not involved. Guests were notified by email in early May and the number affected was not published. Reporting has questioned whether access was continuous across the whole period.

Months of possible access can give an attacker enough guest data for targeted fraud long afterwards. Logging and anomaly detection on applications that hold guest data shorten that window.

Quest Apartment Hotels: customer database accessed through a provider
August 2026

Quest Apartment Hotels, an Australian serviced apartment operator, disclosed on 17 August 2026 that a customer database had been accessed through a vulnerability at a third-party provider. Its September update put the number of customers affected at 1,991,613. What was exposed varied by customer: passport or driver licence numbers for 104,268 people, and card numbers for 344,466, of which 46,727 included the CVV. Quest said scanned passport images were not involved and advised affected customers to replace their passports.

JC Resorts: names and Social Security numbers
January to April 2026

JC Resorts, a US resort management company, said an unauthorised party accessed its network on 19 January 2026. It discovered the breach on 3 March and began sending letters on 28 April to about 5,942 people whose names and Social Security numbers were exposed, offering 24 months of credit monitoring.

Fake Booking.com emails and fake blue screens (PHALT#BLYX)
Campaign, December 2025 to January 2026

Securonix researchers documented a campaign, which they named PHALT#BLYX, aimed at European hospitality businesses. Emails posing as Booking.com cancellations with large euro charges led staff to a fake Booking.com page, a fake CAPTCHA and then a fake Windows blue screen with "recovery" steps. Following those steps meant pasting a command that installed DCRat, a remote access trojan. This is a documented campaign, not a confirmed breach of any named hotel's POS or PMS.

The campaign plays on two front-desk habits: trust in booking emails and the urge to fix an apparent system error quickly. Training should cover fake error screens and instructions to paste commands, as well as ordinary phishing links.

Where the defence gap sits

The VikingCloud survey also asked which controls hotels had in place. Basic tools were common: antivirus and anti-malware (72%), firewalls (70%) and VPNs (66%). Fewer hotels reported penetration testing (28%) or dark-web monitoring (26%). These are self-reported figures from one North American survey, but the pattern matches what we see in assessments: perimeter tools are in place, while account security, supplier access and recovery testing get less attention.

The control gap

Many hotels have perimeter controls aimed at threats that attackers now often route around. Credential misuse, supplier compromise and AI-assisted phishing work in the space between basic perimeter tools and the monitoring that would detect them.

Vulnerability scanning, dark-web monitoring and phishing training all have value, but none of them is enough alone. Dark-web monitoring, for example, finds some exposed credentials, often only after they have been stolen. The table links each main risk to a priority control and the evidence that shows the control is working.

RiskPriority controlEvidence
Stolen PMS or email credentialsMFA, access reviews and sign-in monitoringMFA coverage report and access review results
Compromised supplier accountControlled supplier access and supplier incident proceduresAccess inventory, contract clauses and monitoring records
Ransomware disruptionSegmentation, endpoint protection and tested recoveryRestore test and response exercise reports
Payment card exposurePCI DSS scoping and the controls that applyPayment data flow, responsibility matrix and assessment evidence
Phishing aimed at reservations staffTraining, email security and callback verificationPhishing exercise results and incident records
Unsupported systemsLifecycle inventory and a replacement or mitigation planApproved remediation roadmap

Who owns each control depends on how the hotel is run. In a branded or managed hotel, the brand or head office may run parts of the infrastructure, reservations, loyalty programme and security monitoring. An independent hotel usually carries those responsibilities itself, with its suppliers. Responsibility can be split between the property, the management company, the brand, the PMS or booking engine provider, the payment service provider and external IT suppliers. An assessment should establish who runs each system, who approves changes, who monitors for incidents and who coordinates the response.

Why the gap persists

Several structural factors keep many hotels below the level of protection their risks call for.

Staffing

Hotels compete with financial services, technology and healthcare for the same security professionals, usually with smaller salary budgets. Security often falls to IT generalists, front-office managers or an outsourced provider with a narrow contract.

Budget

Security spending in hospitality tends to follow incidents. A hotel that has not been breached recently is likely to spend on guest-facing technology before infrastructure hardening. After a breach the pattern reverses, and the spending is larger and made under pressure.

Legacy systems

Many hotels run at least one PMS, POS platform or network device that its vendor no longer supports with security updates. Replacing it means capital, downtime and migration risk, so the decision is often deferred. Attackers look for known vulnerabilities in widely used hotel software because patching is slow.

Loyalty programmes

Loyalty accounts have real monetary value: points convert into flights, stays and gift cards. They also hold personal and travel data built up over years. Credential stuffing, which tries username and password pairs leaked from other services, is a common attack on these accounts. Treating loyalty security as a marketing matter leaves exposure that the security team may not be watching.

Supplier contracts

Many hotel supplier agreements lack meaningful security obligations, audit rights and breach notification deadlines, even though suppliers often have access to the PMS, booking platforms and loyalty systems. A hotel that accepts a supplier's assurances without contractual backing has no way to check the security of the systems that process its guests' data.

What 2026 adds to the threat profile

Social engineering with cloned voices and video is now used in real attacks. An attacker can pose as a hotel executive or IT support on a call to get staff to install software or hand over access, and controls designed for text phishing do not cover this. In our experience, front-desk staff, who receive the most contact attempts, get less security training than office staff.

Ransomware groups often steal data as well as encrypting it, and restoring encrypted files does not undo a theft of personal data. Under UK GDPR, a hotel must report a personal data breach to the ICO within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to people. When the risk to guests is high, it must also tell them without undue delay. An incident response plan that names who makes that call saves time when the clock is running.

Where to start

Start with the table above: for each risk, check whether the control exists, who owns it and what evidence shows it works. Our hotel cybersecurity guide covers the attack surfaces and baseline controls in more depth. For an independent view of your current position, the Cyvra Cybersecurity Assessment covers hotel environments and produces a prioritised action list.

How Cyvra can help

Cyvra works with hotels and hospitality groups across the UK and Europe on the risks this report covers. Our work starts with an assessment that maps the attack surface across the business and hotel systems, including PMS, POS, guest Wi-Fi, supplier connections and staff exposure, and produces a prioritised action list.

The assessment works through six areas, applied to how a hotel runs:

  • Business and critical assets: the systems the hotel cannot trade without, such as the PMS, booking engine, channel manager, POS and payment flows, and what an outage or data loss in each would cost.
  • Threat and risk profile: the attack patterns in this report, such as booking-platform phishing, credential theft, ransomware and supplier compromise, scored against your properties, systems and guest data.
  • Security maturity: the controls around the PMS, POS, guest Wi-Fi segmentation, patching, endpoint protection and staff awareness, and whether they are applied the same way at every property.
  • Identity and access: MFA coverage, shared front desk and back office accounts, privileged access, the leavers process for seasonal staff, and remote access for suppliers.
  • Resilience and response: backups and tested recovery for the PMS and booking data, monitoring, and whether your incident response plan would work outside office hours with the hotel full.
  • Third-party and supply chain: which PMS, channel manager, payment and IT suppliers can reach your systems or guest data, what security you require of them, and whether the contracts reflect it.

We map the findings against PCI DSS and UK GDPR, and each finding has a severity rating and remediation guidance. After that we can work with your teams on the findings, as an ongoing vCISO or as a project-based advisor.

If you want to see where your current controls sit against the risks in this report, the Cyvra Cybersecurity Assessment is the starting point. If your hotel has already had an incident or is preparing for a compliance audit, get in touch directly and we can scope the right engagement.

Sources


Ryland Deakin
About the author
Lead Consultant, Cyvra · CISM · CompTIA Security+ · MCP

Ryland has delivered cybersecurity, compliance, and IT management programmes for regulated organisations across the UK and the Netherlands for over 20 years. View full profile

Frequently asked questions

Which parts of a hotel are most targeted by attackers?

Attackers go after the systems that hold guest or payment data or that run daily operations: the PMS, POS terminals in restaurants, bars and spas, booking engines and channel managers, and email. Staff accounts are a common way in, through phishing or reused passwords. Poorly segmented guest Wi-Fi and supplier remote access widen the routes to those systems.

What does Ransomware-as-a-Service mean for hotels in practice?

Ransomware-as-a-Service groups supply ransomware and infrastructure to affiliates who carry out the attacks. Against a hotel, an attack can take reservations, check-in and other operational systems offline, and the pressure is greatest in peak season. Many groups also steal data and threaten to publish it. Paying does not guarantee that the data is deleted or kept private, so the hotel still has to assess the impact of possible exposure.

Does a hotel need penetration testing?

A hotel that accepts cards needs to check which PCI DSS requirements apply to its payment environment. Depending on scope and validation method (for example, which Self-Assessment Questionnaire applies), it may need internal and external penetration testing, segmentation testing or quarterly scans by an Approved Scanning Vendor (ASV), which is a separate activity. A hotel whose card payments are fully outsourced may have fewer requirements. Whatever the formal requirement, testing helps find routes between guest networks, the PMS, POS and supplier connections.

What does UK GDPR require when a hotel suffers a guest data breach?

The hotel must report a personal data breach to the ICO within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to individuals. If it is likely to result in a high risk to guests, the hotel must also tell them without undue delay. The clock starts when the hotel is reasonably certain a breach has occurred, not when the investigation ends. Late reporting is a separate failure: in 2021 the Dutch Data Protection Authority fined Booking.com €475,000 for reporting a 2019 breach 22 days late.

How do smart room IoT devices create network risk?

Smart TVs, digital minibars and room automation run embedded firmware that is updated less often than corporate IT. They connect to the hotel network and may share segments with management systems unless the network is deliberately separated. An attacker who compromises one device gains a foothold, and without segmentation that foothold can lead towards the PMS, POS and back-office tools. Default credentials left unchanged make the first step easier.

Hospitality Cybersecurity

Find out where your hotel's biggest risks are

Our assessment covers POS, PMS, guest Wi-Fi, supplier access and staff exposure across six security domains. You leave with a prioritised action list.

Request an Assessment Hospitality Services