Platform teams gained new native controls and capacity while incident responders contended with active exploitation. AWS expanded pre-ingestion scanning in S3 via GuardDuty, and Samsung issued a fix for an actively exploited Android zero-day, underscoring the need to pair cloud hardening with fast patch cycles. Research into speculative execution raised fresh questions about VM isolation, and investigators detailed sustained data-theft campaigns abusing connected apps in enterprise SaaS.
Platform defenses roll out
AWS widened native malware detection by raising Amazon S3 object scanning limits for GuardDuty Malware Protection from 5 GB to 100 GB and increasing archive processing to 10,000 files. The change reduces blind spots and removes common workarounds such as splitting files or pre-unarchiving content; teams should review IAM, S3 notifications, alert thresholds, and cost impacts before scaling up scanning volumes. In parallel, AWS introduced end-to-end IAM authentication in RDS Proxy for Aurora and RDS MySQL/PostgreSQL, allowing applications to authenticate through the proxy without storing database credentials in Secrets Manager. Centralizing access via IAM policies and temporary tokens can simplify rotations and auditing while retaining the proxy’s connection pooling for serverless and highly concurrent workloads.
Network and service-mesh operations also picked up scale features. Support for 4‑byte AS numbers on virtual interfaces arrived in Direct Connect, removing ASN scarcity constraints and easing multi-tenant and carrier designs; teams should verify downstream router and tooling compatibility before adopting. For microservices, ECS Service Connect now supports cross-account workloads by sharing AWS Cloud Map namespaces via AWS RAM, enabling platform teams to centralize discovery and reduce fragile, duplicated registries across accounts.
Observability and data platforms evolve
Google added native OpenTelemetry Protocol ingestion to Cloud Trace via telemetry.googleapis.com. By preserving the OpenTelemetry data model end‑to‑end, the service increases attribute and span limits and improves queryability with semantic conventions, helping teams standardize pipelines without vendor-specific exporters. Google framed this as a first step toward broader OTLP support across traces, metrics, and logs, with planned managed processing and flexible routing.
On the data tier, AlloyDB moved its Axion-powered C4A instances to general availability, targeting higher transactional throughput and improved price‑performance. AlloyDB on C4A introduces additional vCPU shapes, including a new 48‑vCPU option and a 1‑vCPU/8GB entry shape for lower-cost development, with Google citing benchmarked gains against prior VM families and competitive offerings. For teams balancing performance with cost, the expanded shape portfolio enables more granular right‑sizing for transactional, analytics, and vector-search workloads.
Exploitation pressure and cross‑VM risk
Samsung’s September update remediates a critical out‑of‑bounds write in libimagecodec.quram.so tracked as CVE‑2025‑21043, with exploitation confirmed in the wild. The issue affects Android 13–16 and is fixed in SMR Sep‑2025 Release 1; the vendor did not publish mitigations beyond patching. In parallel, researchers described VMScape (CVE‑2025‑40300), a Spectre‑BTI variant that enables a guest VM to influence branch prediction used by host user‑space components, leaking sensitive data from hypervisors under certain conditions. Reporting in CSO Online highlights a PoC against KVM/QEMU on AMD Zen 4, with Linux introducing an IBPB-on-VMEXIT mitigation that testing suggests imposes marginal overhead. For operators running untrusted tenants, prompt microcode, kernel, and hypervisor updates remain the pragmatic course.
U.S. federal guidance also escalated patch urgency for industrial software. CISA added a remote code execution flaw in DELMIA Apriso (CVE‑2025‑5086) to the Known Exploited Vulnerabilities list, mandating federal remediation and urging swift patching across affected releases. BleepingComputer reports observed exploitation attempts delivering a compressed .NET executable via SOAP requests, with exploitation activity likely automated. Separately, responders warned that the Akira ransomware gang is abusing improperly patched SonicWall SSL VPN deployments (CVE‑2024‑40766) to gain footholds; CSO Online notes many successful intrusions involved outdated firmware and credential hygiene gaps after device migrations. The throughline is consistent: close known holes quickly and rotate credentials where legacy configurations persist.
Data theft via connected apps
The FBI issued a FLASH describing two clusters, UNC6040 and UNC6395, stealing data from Salesforce environments to fuel extortion. According to BleepingComputer, UNC6040 relied on social engineering and malicious OAuth apps to mass‑exfiltrate customer tables, while UNC6395 abused stolen OAuth and refresh tokens tied to integrations such as Salesloft/Drift, then pivoted by harvesting secrets found in support cases. The advisory includes IOCs and reinforces basic guardrails: inventory and monitor connected apps, enforce least privilege and MFA, rotate exposed tokens, and hunt for anomalous API usage. The pattern underscores the importance of treating third‑party SaaS integrations as high‑risk entry points when tokens are compromised.