Industry Category

Cloud Computing

Breach intelligence, attack campaigns, and threat reports targeting the Cloud Computing sector.

7 threat reports
Page 1 of 1
Explore Other Sectors
AccountingAerospaceAerospace/AviationAgricultureAirlines/AviationAnimationApparel/FashionArchitecture/PlanningArtificial IntelligenceArtificial Intelligence/Machine LearningArts/CraftsAutomotiveAviation/AerospaceBanking/MortgageBiotechnology/GreentechBlockchain/CryptocurrencyBroadcast MediaBroadcasting MediaBroadcasting/MediaBuilding MaterialsBusiness Supplies/EquipmentCapital Markets/Hedge Fund/Private EquityChemicalChemicalsCivic/Social OrganizationCivil EngineeringCloud ComputingCloud Computing/SaaSCloud Native Security Fabric (CNSF)Cloud ServicesCommercial FacilitiesCommercial Real EstateComputer GamesComputer HardwareComputer NetworkingComputer Software/EngineeringComputer/Network SecurityConstructionConsultingConsumer ElectronicsConsumer GoodsConsumer ServicesCosmeticsCosmeticsCritical ManufacturingCryptocurrenciesCryptocurrencyCustomer ServicesCybersecurityDairyDating/Personal ServicesDating/Social PlatformsDefense/SpaceDesignE-LearningEducation ManagementElectrical/Electronic ManufacturingEmergency ServicesEnergyEnergy/Oil/Solar/GreentechEntertainment/Movie ProductionEnvironmental ServicesEvents ServicesExecutive OfficeFacilities ServicesFarmingFashion/ApparelFinancial ServicesFine ArtFisheryFood ProductionFood/BeveragesFortune 500 companiesFranchisingFundraisingGambling/CasinosGamingGaming/CasinosGovernment AdministrationGovernment FacilitiesGovernment RelationsGraphic Design/Web DesignHealth Care / Life SciencesHealthcareHigher Education/AcadamiaHospitalityHospitalsHuman Resources/HRImport/ExportIndividual/Family ServicesIndustrial AutomationInformation ServicesInformation Technology/ITInsuranceInternational AffairsInternational Trade/DevelopmentInternetInvestment Banking/VentureInvestment Management/Hedge Fund/Private EquityJudicialJudiciaryLaw EnforcementLaw Practice/Law FirmsLegal ServicesLegislative OfficeLeisure/TravelLogistics/ProcurementLuxury Goods/JewelryMachineryManagement ConsultingManufacturingMaritimeMarket ResearchMarketing/Advertising/SalesMechanical or Industrial EngineeringMedia ProductionMedical EquipmentMedical PracticeMilitary IndustryMining/MetalsMobileMuseums/InstitutionsMusicNewspapers/JournalismNon-Profit/VolunteeringOil/Energy/Solar/GreentechOnline PublishingOther IndustryOutsourcing/OffshoringPackage/Freight DeliveryParkingPharmaceuticalsPhilanthropyPhotographyPlasticsPolitical OrganizationPrimary/Secondary EducationProfessional ServicesProfessional TrainingPublic Relations/PRPublic SafetyPublishing IndustryRailroad ManufactureReal Estate/MortgageRecreational Facilities/ServicesReligious InstitutionsRenewables/EnvironmentResearch IndustryRestaurantsRetail IndustryRoboticsRural HealthcareSecurity/InvestigationsSemiconductorsShipbuildingSocial Media/InternetSporting GoodsSportsStaffing/RecruitingSupermarketsTechnologyTechnology/ITTelecommunicationsThink TanksToys and GamesTransportationTravel/TourismTrucking/FreightUtilitiesVenture Capital/VCWarehousingWater and Waste ManagementWater and WastewaterWater and Wastewater SystemsWater and Wastewater TreatmentWater TreatmentWater, Waste, Steam, and Air Conditioning ServicesWater/Waste ManagementWater/WastewaterWater/Wastewater ManagementWater/Wastewater/UtilitiesWholesaleWine/SpiritsWirelessWriting/Editing

Cloud Computing Threat Reports

Showing 1–7 / 7 reports
Critical Xen Orchestra Auth Bypass (VSA-2026-062): How Attackers Seized Root Control of Entire Hypervisor Fleets
Critical Xen Orchestra Auth Bypass (VSA-2026-062): How Attackers Seized Root Control of Entire Hypervisor Fleets

Critical Xen Orchestra Auth Bypass (VSA-2026-062): How Attackers Seized Root Control of Entire Hypervisor Fleets

In November 2026, threat actors began actively exploiting a critical authentication bypass vulnerability (VSA-2026-062) in Vates VMS's Xen Orchestra virtualization management platform. By sending a specially crafted cookie containing an empty JSON object as the authentication token, attackers could bypass all authentication controls and obtain full administrative privileges without valid credentials. Once inside, adversaries achieved arbitrary code execution on managed hypervisor pools and complete root-level takeover of XCP-ng nodes. Active exploitation was confirmed via a known RedLine Stealer C2 IP address and a TOR-based exfiltration endpoint, with forensic indicators including rogue virtual machines and persistent cron-based backdoors deployed across compromised infrastructure. This incident underscores a broader trend of attackers targeting virtualization management planes—the control layer governing entire server fleets—where a single authentication flaw translates directly into full infrastructure compromise. As enterprises consolidate workloads onto hypervisor platforms, unauthenticated admin-level access vulnerabilities in these systems represent maximum-blast-radius risks that demand immediate patching, network segmentation, and internet exposure controls.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(high)
C&CCommand & Control(high)
EExfiltration(medium)
IImpact(medium)
Read report
Qubole AWS IAM Breach 2026: How Trusted Cloud Access Became an Attack Vector
Qubole AWS IAM Breach 2026: How Trusted Cloud Access Became an Attack Vector

Qubole AWS IAM Breach 2026: How Trusted Cloud Access Became an Attack Vector

Between October 14 and October 26, 2026, an unknown threat actor abused compromised credentials tied to Qubole's AWS account (ID: 805246085872) to execute cross-account AssumeRole attacks against multiple Qubole customers. The attacker leveraged valid External IDs—visible in CloudTrail logs and infrastructure-as-code files—to assume IAM roles originally provisioned for Qubole's data lake platform, even in accounts where Qubole was no longer actively used. Once inside, the attacker harvested Lambda environment variables, Secrets Manager entries, SSM Parameter Store values, Okta and Entra ID credentials, and exfiltrated entire S3 buckets. A separate but related campaign from October 8–11 abused static AWS access keys configured for Qubole. The incident underscores how dormant third-party IAM roles with overly broad permissions create persistent, exploitable trust relationships across cloud environments. This attack exemplifies the accelerating threat of supply-chain credential abuse in multi-tenant cloud platforms. As enterprises deepen reliance on SaaS data platforms with deep AWS integration, the attack surface of inherited trust relationships expands dramatically—making third-party IAM hygiene and cross-account visibility critical priorities for cloud security programs in 2026 and beyond.

Critical impact

Kill Chain

ICInitial Compromise(medium)
PEPrivilege Escalation(high)
LMLateral Movement(high)
C&CCommand & Control(high)
EExfiltration(high)
IImpact(medium)
Read report
OpenSSH *sshole: How a 2016 Patch Created a 2026 Cloud Root Takeover Risk

OpenSSH *sshole: How a 2016 Patch Created a 2026 Cloud Root Takeover Risk

A newly disclosed authentication bypass vulnerability, dubbed *sshole, affects OpenSSH servers running on musl-based Linux distributions such as Alpine Linux, OpenWrt, Buildroot, and Yocto. Discovered by security researcher Ozgun Kultekin and disclosed in November 2026, the flaw exploits a logic error introduced in a 2016 OpenSSH patch for CVE-2016-6210. When an attacker submits an oversized password exceeding musl's 256-byte crypt() limit, the library returns an asterisk (*), which OpenSSH then incorrectly matches against accounts whose password field is also set to * to disable logins—granting unauthorized access. Alpine Linux's official AWS and Azure cloud images are particularly exposed, as the default 'alpine' account carries passwordless doas privileges, enabling full root escalation. This vulnerability is especially urgent for cloud-native and container-centric organizations that rely heavily on Alpine Linux as a minimal base image. The flaw has silently existed since 2016, underscoring how legacy patch decisions in foundational infrastructure components can create long-lived, high-impact attack surfaces. With cloud workloads proliferating across hybrid environments, SSH authentication integrity is a critical zero trust dependency.

Medium impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(low)
Read report
CVSS 10.0: How a Single Public Certificate Unlocks Root Access in LXD and MicroCloud
CVSS 10.0: How a Single Public Certificate Unlocks Root Access in LXD and MicroCloud

CVSS 10.0: How a Single Public Certificate Unlocks Root Access in LXD and MicroCloud

A maximum-severity vulnerability (CVE-2026-112816, CVSS 10.0) in Canonical's LXD container hypervisor and MicroCloud clustering platform allows a network-adjacent attacker to impersonate any trusted client without possessing that client's private key. By exploiting a flaw in mutual-TLS certificate-chain validation, an attacker who obtains a trusted client's public certificate—information that is not secret—can attach it to their own TLS handshake and be accepted as that client. If the impersonated identity carries administrative rights, the attacker gains root access to the underlying host. Canonical released fixed snap versions (LXD 6.10.1, 5.21.9, 5.0.11, 4.0.15; MicroCloud 3.4.1, 2.1.5) following disclosure by the Incus community fork, which patched the same flaw in version 7.6.0. This incident underscores a growing pattern of authentication-bypass flaws in cloud-native infrastructure control planes. As organizations scale containerized and clustered workloads, improperly validated identity in east-west API paths creates a silent privilege-escalation highway—an attack surface that perimeter firewalls and endpoint agents alone cannot address.

Critical impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(low)
EExfiltration(medium)
IImpact(low)
Read report
Tailworm 2026: How Eleven Tailscale SSH Flaws Put Root Access One Hop Away
Tailworm 2026: How Eleven Tailscale SSH Flaws Put Root Access One Hop Away

Tailworm 2026: How Eleven Tailscale SSH Flaws Put Root Access One Hop Away

In October 2026, Cyberdione Labs disclosed eleven vulnerabilities—collectively named Tailworm—affecting Tailscale 1.104.2 and the self-hosted headscale v0.29.5 control server. The most critical flaw resides in Tailscale's embedded SSH server, which runs as root, and allows an authorized device with a single SSH policy rule to exploit Unix-socket forwarding race conditions to gain full root code execution on target servers, capture enrollment keys, and delete arbitrary files. Additional flaws enable credential theft via cloud metadata through misconfigured app connectors, unauthenticated denial-of-service against the headscale control plane, and client memory exhaustion via malicious DERP relay responses. Tailscale confirmed the findings are serious and committed to shipping patches by end of day October 27, 2026. The Tailworm disclosure arrives as enterprises increasingly rely on software-defined mesh VPNs to connect hybrid and multi-cloud workloads, expanding the blast radius of privilege-escalation flaws. The attack chain—authorized user to root in a single hop—mirrors a broader industry trend where identity-permissioned access replaces perimeter controls without compensating runtime segmentation, making zero-trust policy enforcement and east-west traffic controls more urgent than ever.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(medium)
EExfiltration(medium)
IImpact(high)
Read report
mdrfckr Campaign Adopts Updated SSH Client in April 2026 Attacks

mdrfckr Campaign Adopts Updated SSH Client in April 2026 Attacks

Between April 14 and April 21, 2026, a DShield sensor detected 24 unique IP addresses executing the 'mdrfckr' campaign, a known botnet operation active since 2018. The attackers utilized the SSH client banner 'SSH-2.0-libssh_0.11.1' and produced the hassh fingerprint '03a80b21afa810682a776a7d42e5e6fb', indicating an evolution in their tooling. The campaign's tactics, including writing a persistent SSH key and executing reconnaissance commands, remained consistent with previous observations. This incident underscores the adaptability of threat actors in updating their tools while maintaining established attack methodologies. Organizations should enhance their detection capabilities to identify new SSH client fingerprints associated with known malicious campaigns.

High impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(high)
LMLateral Movement(medium)
C&CCommand & Control(high)
EExfiltration(low)
IImpact(high)
Read report
Inexpensive Hardware Bypass Exposes Flaws in AMD & Intel Memory Encryption (2024)
Financial Services10 months ago

Inexpensive Hardware Bypass Exposes Flaws in AMD & Intel Memory Encryption (2024)

In early 2024, security researchers unveiled a significant vulnerability impacting AMD and Intel CPUs implementing memory encryption for confidential computing. By constructing an inexpensive hardware module, the team demonstrated how attackers could physically intercept and decrypt protected memory traffic between the main processor and RAM, effectively bypassing hardware-implemented encryption intended to secure sensitive workloads. This attack, which operates independently of software measures, exposes plaintext data and private keys, revealing a critical flaw in the foundation of memory encryption technologies relied upon for cloud, data center, and edge security. As a result, organizations using these processors for confidential computing may be at risk until hardware changes are introduced. This research underscores increasing scrutiny of hardware-level threats as confidential computing gains adoption. With the emergence of accessible hardware-based attacks, enterprises and regulators face renewed urgency to evaluate physical and low-level protections beyond traditional network and endpoint security controls.

Low impact

Kill Chain

ICInitial Compromise(high)
PEPrivilege Escalation(medium)
LMLateral Movement(medium)
C&CCommand & Control(low)
EExfiltration(medium)
IImpact(low)
Read report
[ INCIDENT RESPONSE // UNDER ATTACK? ]

Stop Active Cloud Data Exfiltration

Aviatrix Rapid Containment helps teams instantly identify what data is leaving the environment, from which workload, and where it’s going — during an active breach.

Looking for threats in a different sector?

Browse All Threat Reports