Misconfiguration remains one of the leading threats to cloud environments because a single configuration error can result in public network access, unrotated keys, missing encryption, exposed services, and logging gaps. CISA now mandates baseline cloud configuration practices for US federal agencies. More than two-thirds of midmarket organizations use multiple cloud providers, each with its own se

A new report from Intruder, the 2026 Cloud Security Index, indicates that misconfigurations continue to be a primary threat to cloud environments, with a single error potentially leading to public network access, unrotated keys, or exposed services. The report highlights that weak identity and access management (IAM) controls and inadequate logging and alerting are the most pervasive security issues across major cloud providers, impacting 80% to 98% of accounts.
The study notes that over two-thirds of midmarket organizations utilize multiple cloud providers, each with distinct security models and configuration settings. This complexity means that a single security issue can manifest differently across AWS, Azure, and Google Cloud, often requiring varied identification and remediation strategies. The report challenges the assumption that cloud migration inherently provides security, emphasizing that each platform has unique vulnerabilities that security teams must specifically address.
Across the three major cloud platforms, the most common security issues vary based on their architectural differences. AWS environments frequently experience misconfigurations related to storage, network access, and identity management. Azure's primary concerns revolve around storage security and identity protection, specifically citing unrotated access keys, publicly accessible storage, and a lack of multi-factor authentication (MFA). Google Cloud environments are predominantly affected by IAM weaknesses, including missing MFA, unused service accounts, and overly permissive service accounts.
Weak identity controls, excessive permissions, and incomplete or insecure configurations are identified as consistent sources of cloud security risk across all three providers. AWS showed the highest prevalence of misconfigurations in five of the six security categories analyzed, including permissive firewalls, exposed services, and weak encryption. Azure had the highest rate of misconfigured services. Google Cloud recorded the lowest prevalence in four of the six categories. The report points out that exposed services exhibited the widest variation, affecting 76% of AWS accounts, 64% of Azure accounts, and 8% of Google Cloud accounts, attributing these differences to the breadth of service portfolios and varying approaches to secure default configurations.
Cloud security posture also correlates with organization size. Larger enterprises generally report fewer issues with permissive firewalls, exposed services, and weak encryption, suggesting more mature security processes and greater investment. However, IAM presents a unique challenge that escalates with scale. Weak IAM controls affect 87% of small and medium-sized enterprises (SMEs), 95% of midmarket organizations, and 98% of large enterprises, a trend attributed to the increasing complexity of managing users, roles, and permissions in larger environments.
Remediation times also vary by organization size. Smaller organizations typically resolve cloud misconfigurations within an average of 8 to 16 days. The average remediation time peaks at 35 days for organizations with 1,000 to 5,000 employees, then decreases to 19 days for those with 5,000 to 10,000 employees, and further drops to 10 days for the largest enterprises. Midmarket organizations often manage cloud environments comparable to enterprises but without the dedicated security resources available to larger companies. The Cybersecurity and Infrastructure Security Agency (CISA) now mandates baseline cloud configuration practices for US federal agencies.

JetBrains is urging Cadence users to revoke and rotate all credentials following a security incident last month in which unidentified threat actors exploited a recently disclosed critical vulnerability in TeamCity to breach its own environment. "Cadence users should immediately revoke or rotate all credentials and secrets that may have been used to run their Cadence executions," JetBrains said.
A weakness has been identified in Tenda CP3 27.5.57.101. This issue affects some unknown processing of the file Net/NetCheckPing.cpp. This manipulation of the argument interface_name/host causes os command injection. The attack can be initiated remotely.
A security flaw has been discovered in Tenda CP3 27.5.57.101. This vulnerability affects the function SystemAsh of the file Apis/system.c of the component Kylin. The manipulation of the argument AlarmVoiceURL results in os command injection. It is possible to launch the attack remotely.

OpenAI has announced a $1 billion commitment to provide subsidized access to its Daybreak AI cybersecurity tools for under-resourced critical infrastructure defenders. The initiative, named Daybreak for Frontline Defenders, will offer AI models, training, and technical support over the next six months, prioritizing water and wastewater utilities, electric grid operators, and local government entities. This move aims to equip organizations with limited budgets and staff against increasingly sophisticated cyber threats.

Attackers are exploiting a new unpatched vulnerability in Magento Open Source and Adobe Commerce that lets them run malicious code on an online store's server without logging in, Dutch e-commerce security company Sansec said in an advisory published on September 5. Sansec, which discovered the flaw and named it StyleSmuggler, said attacks started on September 4. "Sansec is publishing early
In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit architectures.