Skip to content

Cloud Security Statistics 2026: How Cloud Environments Get Breached

Cloud security statistics for 2026 from Google Cloud, CrowdStrike, Thales, IBM and Verizon: entry vectors, credential theft, encryption gaps and AI workloads.

Omar KhandakerBy , Senior Security ConsultantUpdated 10 min read

Cloud Penetration TestingFrom $6,800Fixed scope, free retest, no hourly billing.

Get my fixed price

Cloud breaches used to be a story about weak passwords and open storage buckets. The 2026 data says that story has changed: unpatched third-party software running in the cloud is now the leading entry point, credential theft is still rising, and the gap between a vulnerability being published and being exploited at scale has collapsed to days. This page collects the measured figures from Google Cloud’s Threat Horizons report, CrowdStrike’s Global Threat Report, the Thales Data Threat Report, IBM’s Cost of a Data Breach and Verizon’s DBIR, each linked to its source. We update the page as each is published.

How to cite: link to this page or to the primary source beside each figure. Survey figures carry their sample size.

Key statistics at a glance

  • 44.5% of cloud intrusions in the second half of 2025 started with a third-party software vulnerability, up from 2.9%. (Google Cloud Threat Horizons, H1 2026)
  • 27.2% started with weak or absent credentials, down from 47.1%. (Google Cloud, H1 2026)
  • 48 hours: React2Shell (CVE-2025-55182) was exploited within 48 hours of disclosure. (Google Cloud, H1 2026)
  • 67% of organizations see credential theft rising against their cloud infrastructure. (Thales 2026)
  • More than 20% of organizations reported a breach of their AI models or applications. (IBM 2026)

Summary table: cloud security statistics 2026

Statistic Value Source Data period
Cloud intrusions that began with a third-party software vulnerability 44.5% Google Cloud Threat Horizons, H1 2026 Second half of 2025
Cloud intrusions that began with weak or absent credentials 27.2%, down from 47.1% Google Cloud, H1 2026 Second half of 2025
Cloud intrusions that began with a misconfiguration 21%, down from 29.4% Google Cloud, H1 2026 Second half of 2025
Time from disclosure to exploitation of React2Shell About 48 hours Google Cloud, H1 2026 December 2025
Growth in cloud-conscious intrusions 37% CrowdStrike 2026 2025
Organizations that see credential theft rising against their cloud 67% Thales 2026 Survey, 3,120 respondents
Sensitive cloud data that is encrypted 47% Thales 2026 Survey, 3,120 respondents
New secrets leaked in public GitHub commits 28.65 million, up 34% GitGuardian 2026 2025
Organizations still using long-lived IAM user credentials for AWS console access 37% Datadog 2026 September 2026
Organizations reporting a breach of their AI models or applications More than 20% IBM 2026 2026 report

1. How cloud environments are breached

  • Exploitation of vulnerabilities in third-party software was the primary entry vector in 44.5% of cloud intrusions in the second half of 2025, up from 2.9% in the first half: the first time it overtook stolen credentials since the report began. (Google Cloud Threat Horizons Report, H1 2026)
  • Weak or absent credentials fell from 47.1% of entry vectors to 27.2% over the same period. (Google Cloud Threat Horizons, H1 2026)
  • The window between a vulnerability’s public disclosure and mass exploitation in the cloud collapsed by an order of magnitude, from weeks to days. React2Shell (CVE-2025-55182) was exploited within 48 hours of disclosure in December 2025, with cryptominers deployed at the same speed. (Google Cloud Threat Horizons, H1 2026)
  • Cloud-conscious intrusions rose 37% in 2025, and cloud targeting by state-linked actors rose 266%. (CrowdStrike 2026 Global Threat Report)
  • 67% of organizations see credential theft and misappropriated secrets increasing against their cloud infrastructure. (Thales 2026 Data Threat Report, 3,120 respondents)
  • 48% of all breaches involved a third party, including SaaS providers, cloud platforms and OAuth integrations, a 60% increase in one year. (Verizon 2026 Data Breach Investigations Report)
  • Among ransomware attacks that began with an exploited vulnerability, stolen credentials or brute force, 38% started in exposed applications and systems, ahead of user devices (30%), firewalls (21%) and VPNs (8%). (Sophos State of Ransomware 2026, 2,158 organizations)

What this means for testing: a cloud penetration test that only reviews IAM policies misses the vector that now leads. The scope has to include every internet-facing workload and the software running on it. See cloud penetration testing for how we scope AWS, Azure and GCP engagements, and the cloud penetration testing cost page for the price tiers, from $6,800.

2. Cloud misconfiguration and exposure statistics

Misconfiguration, exposed interfaces and leaked secrets are the classic cloud failures. They are declining as entry points but have not gone away.

  • Misconfiguration was the entry vector in 21% of the Google Cloud incidents analyzed for the second half of 2025, down from 29.4% in the first half. Exposed sensitive user interfaces or APIs fell from 11.8% to 4.9%. Google credits automated guardrails for the decline. (Google Cloud Threat Horizons, H1 2026)
  • 37% of organizations still use long-lived credentials, in the form of IAM users, to access the AWS console, and only 55% implement data perimeters, up from 40% in 2025. (Datadog State of Cloud Security 2026, a sample of thousands of organizations on AWS, Azure and Google Cloud)
  • 28.65 million new secrets were detected in public GitHub commits in 2025, up 34% in a year. 1.28 million of them were credentials for AI services, up 81%. (GitGuardian State of Secrets Sprawl 2026)
  • Leaked secrets stay usable: 64% of the valid secrets GitGuardian detected in 2022 were still active four years later, and 32.2% of internal repositories contained at least one hardcoded secret against 5.6% of public ones. (GitGuardian 2026)
  • Fixes are slow. Only 23% of third-party organizations fully remediated missing or improperly secured MFA on their cloud accounts, and for weak passwords and permission misconfigurations it took almost eight months to resolve half of the findings. (Verizon 2026 DBIR)

What this means for testing: these are configuration findings, and they can be checked without exploiting anything. A read-only cloud security assessment reviews one account’s identity, storage, network and logging settings, from $4,200.

3. Identity in the cloud

  • More than 97% of identity attacks are password attacks, and identity-based attacks rose 32% in the first half of 2025. Phishing-resistant MFA blocks over 99% of them. (Microsoft Digital Defense Report 2025)
  • 79% of ransomware attacks began with an identity-based approach; 97% of victims where compromised credentials were the root cause had MFA enabled in some form at the time of the attack. (Sophos 2026)
  • Credential abuse appeared somewhere in 39% of breaches even though it was the initial vector in only 13%. (Verizon 2026 DBIR)
  • The average eCrime breakout time, from a first foothold to lateral movement, fell to 29 minutes; the fastest was 27 seconds. In cloud environments that movement is an API call, not a network hop. (CrowdStrike 2026)

See what a real pentest finds. Read our sample report, then get a fixed quote in writing.

4. Data in the cloud

  • Only about half of sensitive data stored in the cloud is encrypted: 47%. (Thales 2026)
  • Only 34% of organizations say they know where all their data resides, and 39% can fully classify it. (Thales 2026)
  • Human error was named the leading cause of breach by 28% of organizations. (Thales 2026)
  • 63% of intrusions involved data theft, by Microsoft’s count. (Microsoft Digital Defense Report 2026)
  • Breaches through the supply chain took the longest to identify and contain, 258 days against 247 for all breaches. (IBM Cost of a Data Breach Report 2026, 602 organizations)

5. AI workloads, the new cloud attack surface

  • More than 20% of organizations reported a breach targeting their AI models or applications. The leading causes were compromised APIs, applications or plug-ins (27%) and cloud misconfigurations affecting AI workloads (27%). (IBM 2026)
  • 61% of organizations rank AI as their top data security risk, and 61% say their AI applications are being targeted, with sensitive data the leading target. (Thales 2026)
  • Shadow AI incidents affected 43% of breached organizations, up from 20% a year earlier; employees using unapproved AI tools tripled from 15% to 45%. (IBM 2026; Verizon 2026 DBIR)
  • AI-enabled breaches averaged $6 million, about $1 million above the overall average, and were one in four malicious breaches. (IBM 2026)
  • AI-enabled adversary operations increased 89% year over year. (CrowdStrike 2026)

Our AI and LLM penetration testing service covers the model, the application around it, and the cloud plumbing underneath. For real cases behind the credential figures, see our write-up of LLMjacking and stolen AI keys.

6. The cost of getting it wrong

  • The global average breach cost $4.99 million in 2026 and $11.5 million in the United States. Financial services averaged $6.3 million. (IBM 2026)
  • Mean time to identify and contain a breach was 247 days; breaches over 200 days cost $5.65 million against $4.32 million for shorter ones. (IBM 2026)
  • Only 26% of known exploited vulnerabilities were fully remediated in 2025, down from 38%, and the median time to remediate rose to 43 days, which is the same window attackers now close in 48 hours. (Verizon 2026 DBIR)
  • 42% of vulnerabilities exploited by adversaries in 2025 were exploited before public disclosure. (CrowdStrike 2026)

7. What the numbers say to do

These four steps are the testing view. The control-by-control version is in our cloud security best practices checklist.

  1. Inventory every internet-facing workload and the software on it. The leading cloud entry vector is now a known vulnerability in third-party software. A cloud penetration test starts with that inventory, from outside, the way an attacker would.
  2. Assume any credential can leak. 67% see credential theft rising. Test what a leaked developer key or an over-permissive role can reach; that assumed-breach scenario is the second half of our cloud engagement.
  3. Patch on the attacker’s clock, not the audit’s. 48 hours to exploitation against a 43-day median to remediate is the whole problem in two numbers. Prioritize by exposure, not by CVSS alone; our guide to vulnerability remediation shows how to rank with KEV and EPSS.
  4. Test the AI stack like any other application. 27% of AI breaches came through the APIs and plug-ins around the model, and another 27% through cloud misconfiguration. Both are ordinary findings in an API penetration test.

Our AWS penetration testing guide covers what AWS allows, how to scope it, and what gets tested, and our GCP penetration testing guide does the same for Google Cloud. For Microsoft’s cloud, see the Azure penetration testing guide.

Frequently asked questions

What is the top cause of cloud breaches in 2026? Exploited vulnerabilities in third-party software. They were the entry point in 44.5% of the Google Cloud incidents analyzed for the second half of 2025, ahead of weak or absent credentials (27.2%) and misconfiguration (21%).

What percentage of cloud breaches involve misconfiguration? 21% of the Google Cloud incidents in the second half of 2025 began with a misconfiguration, down from 29.4% in the first half. Another 4.9% began with an exposed sensitive interface or API.

How much does a cloud breach cost? The global average cost of a data breach was $4.99 million in 2026 according to IBM, a figure that covers every environment. AI-enabled breaches averaged $6 million.

How quickly are cloud vulnerabilities exploited? Within days. Google Cloud observed cryptominers deployed within about 48 hours of the public disclosure of CVE-2025-55182, while Verizon found the median time to fully remediate a known exploited vulnerability was 43 days.

Part of our cybersecurity statistics hub. See also data breach statistics and ransomware statistics.

Sources

Omar Khandaker

Written by

Omar Khandaker, Senior Security Consultant

11+ years in the field. Focus: PCI DSS, ISO 27001, ISO 9001 & CMA. Part of the team that scopes, tests, and reports for our clients. Full profile →

Find out what an attacker sees.

Tell us what to test and see your fixed price.

Prefer the full scoping questionnaire? 
Start the conversation

Get a quick proposal

We are online