Coverage: Last 24 hours

Today’s Highlights

Several severe vulnerabilities and threat trends emerged this cycle, including unauthenticated remote project deletion in GitLab, automation workflow compromise in a public Snowflake repository, critical WordPress RCE, advanced C2 infrastructure, and incidents exposing the fragility of both user authentication and AI operational controls. Defenders must prioritize rapid response but also recognize the shifting attack surface across SaaS integrations, AI agents, and widely deployed open source stacks.

Defensive Actions

• Patch all GitLab CE/EE instances to address CVE-2026-19478 immediately, prioritizing any internet-exposed deployments.
• Deploy patch for CVE-2026-15748 on all WordPress sites running Forminator Forms.
• Audit .github/workflows/jira_issue.yml or similar workflow files for unsafe context handling and public triggers.
• Rotate and audit privileged credentials for administrative and integration accounts, especially in government and financial environments.
• Monitor DNS logs and Google Apps Script API activity for anomalous patterns aligned with recent C2 techniques.
• Review IAM policies and restrict permissions on MCP servers and AI agent infrastructure.
• Restrict file upload permissions and hunt for malicious PHP scripts in webroots of all WordPress installations.
• Segregate development and production AI integrations and deploy approval workflows for any automated actions initiated by AI.
• Perform secret scanning and implement runtime isolation for new AI agent/server deployments.
• Deploy behavioral anomaly detection for large data accesses in sensitive systems such as tax/payment authorities.

Table of Contents

1. 680,000 Impacted by French Tax Authority Data Breach
2. ⚡ Weekly Recap: VMware Exploits, Windows 0-Day, MCP Attacks, Browser Hijacks and More
3. Unisoc VoLTE Video Call Exploit Chain Can Give Attackers Full Android Kernel Access
4. Evooo1Bot Linux Botnet Exploits Known Flaws to Turn Edge Devices Into SOCKS5 Proxies
5. Suspected China-Nexus Actor Exploits VMware vCenter Flaw, Deploys Babuk-Derived Ransomware
6. Critical GitLab GraphQL Flaw Could Let Unauthenticated Attackers Delete Public Projects
7. Snowflake GitHub Actions Flaw Lets Crafted Issues Trigger Command Injection
8. Forminator WordPress Flaw Can Enable Unauthenticated RCE via Malicious PHP Uploads
9. Cavern C2 Uses DNS and Google Apps Script to Blend Into Legitimate Traffic
10. How MCP Servers Can Expose Enterprise Secrets

Top Stories

680,000 Impacted by French Tax Authority Data Breach

Source: SecurityWeek | Risk: HIGH | Impacted: National and regional government agencies, Enterprises storing citizen or tax data, Users of tax authority online services

Summary: Hackers used compromised credentials to access enterprise and personal tax-related data. The post 680,000 Impacted by French Tax Authority Data Breach appeared first on SecurityWeek.

Why it matters: A single credential compromise can expose sensitive financial data at national scale, highlighting the persistent risk to critical government services and potential downstream fraud or identity theft.

Practitioner Perspective

French tax authority systems were breached via compromised credentials, enabling access to substantial volumes of enterprise and personal information. This underscores a decades-old problem: perimeter and user authentication weaknesses remain a top risk for high-value government data. Attackers will continue to focus on credential theft and spray to exploit privileged system access, especially where legacy applications or unmonitored interfaces persist. Security teams supporting critical infrastructure or sensitive personal data should not assume user authentication alone is an adequate barrier. Proactive credential protections and out-of-band monitoring are now mandatory to prevent similar mass breaches.

Recommended Actions

• Require strong multi-factor authentication for all sensitive French tax authority system access points
• Rotate and audit privileged credentials for administrative and integration accounts

Exploits & CVEs

⚡ Weekly Recap: VMware Exploits, Windows 0-Day, MCP Attacks, Browser Hijacks and More

Source: The Hacker News | Risk: HIGH | Impacted: Broadly: users of exposed enterprise/cloud services, organizations with unpatched endpoints

Summary: The expensive attacks are not always the clever ones. This week had plenty of proof. Exposed services got hit, old bugs found fresh use, browser sessions became attack paths, and supply-chain problems kept spreading farther than the original compromise. A lot of it came down to access that was already there and defenses that assumed nobody would look too closely.

Why it matters: Ubiquitous vulnerabilities remain easily discoverable and rapidly weaponized, emphasizing the critical importance of closing well-known exposures even as new threat vectors emerge.

Practitioner Perspective

Security teams cannot deprioritize longstanding patches or rely solely on novel attack signatures; attackers continue to exploit common weaknesses, leveraging exposure and access that defenders left unmonitored. The proliferation of supply chain and session-hijacking risks means a sustained focus on attack surface reduction and configuration hygiene remains essential. Prioritize immediate patching and review of external-facing and legacy systems before considering them low risk.

Recommended Actions

• Run complete vulnerability assessments on legacy and external-facing systems using prioritized CVE lists
• Deploy anomaly detection to monitor for exploited access patterns

Unisoc VoLTE Video Call Exploit Chain Can Give Attackers Full Android Kernel Access

Source: The Hacker News | Risk: HIGH | Impacted: Android devices running Unisoc modem firmware, mobile operators, IoT/embedded Android devices

Summary: Security researchers at SSD Secure Disclosure have published a two-stage exploit chain that achieves full Android kernel access on devices running Unisoc modem firmware through a VoLTE video call, with no fix from the chipset maker. The advisory, published August 17, 2026, is the second stage of a chain that began in March 2026, when SSD disclosed remote code execution in the…

Why it matters: The lack of patch for this VoLTE exploit chain leaves millions of Android devices vulnerable to potential full device takeover simply through a crafted video call.

Practitioner Perspective

Any fleet containing Unisoc-powered devices is at heightened risk, with open RCE and kernel-level exploits circulating publicly and no fix from the vendor. The attack chain relies solely on network exposure, enabling adversaries to bypass all user intervention. Risk management should include immediate device inventory, policy workarounds, and rapid assessment for alternative mitigations while the supply chain remains exposed.

Recommended Actions

• Inventory all Unisoc-based devices and enforce VoLTE call restrictions until vendor patches are available
• Deploy network monitors for anomalous call behaviors targeting vulnerable devices

Evooo1Bot Linux Botnet Exploits Known Flaws to Turn Edge Devices Into SOCKS5 Proxies

Source: The Hacker News | Risk: HIGH | Impacted: Edge device owners, network admins, ISPs, IoT infrastructure

Summary: Cybersecurity researchers have flagged a previously undocumented Linux botnet family dubbed Evooo1Bot that derives its core functionality from the Mirai botnet source code and is equipped to turn internet-facing devices into SOCKS proxies. “While the malware reuses the DDoS engine from the publicly leaked Mirai source code, it extends the original framework with numerous capabilities, including…

Why it matters: Compromised edge devices are now routinely transformed into general-purpose proxy networks for subsequent crimeware, undermining trust and monitoring at the network perimeter.

Practitioner Perspective

Defenders with high volumes of exposed Linux hosts or IoT must assume brute-force botnet recruitment is ongoing. Evooo1Bot campaigns blend DDoS heritage with advanced proxy infrastructure, increasing relay opportunities for both crime and advanced persistent threats. Prioritize external scan closure and implement automated remediation for detected proxying or unknown external connections.

Recommended Actions

• Close inbound access on unneeded services and continuously scan for exposed Linux/IoT endpoints
• Monitor external network connections for SOCKS5 proxy activity, especially from small office/home office devices

Suspected China-Nexus Actor Exploits VMware vCenter Flaw, Deploys Babuk-Derived Ransomware

Source: The Hacker News | Risk: HIGH | Impacted: VMware vCenter Server users, organizations with virtualized infrastructure

Summary: Cybersecurity researchers have attributed the exploitation of a newly patched security flaw in Broadcom VMware vCenter to a suspected China-nexus advanced persistent threat (APT). The attacks involve the exploitation of CVE-2026-59310 (CVSS score: 9.8), a severe directory-traversal vulnerability in the VMware vCenter server that could be weaponized by a malicious actor to execute arbitrary code…

Why it matters: Exploitation of recent VMware flaws by state-aligned adversaries demonstrates the rapid pivot from patch disclosure to active ransomware deployment targeting enterprise virtualization.

Practitioner Perspective

Virtualized environments must be treated as critical attack surfaces. With active exploitation of CVE-2026-59310 (CVSS 9.8) confirmed, organizations running VMware vCenter Server risk catastrophic loss of service and lateral movement. APT playbooks now blend ransomware and supply chain disruption, making rapid patching and exhaustive audit logs of privileged actions essential.

Recommended Actions

• Patch VMware vCenter for CVE-2026-59310 (CVSS 9.8) on all production and test clusters
• Review admin access logs for anomalous or script-driven actions since vulnerability disclosure

Emerging Signals

Critical GitLab GraphQL Flaw Could Let Unauthenticated Attackers Delete Public Projects

Source: The Hacker News | Risk: CRITICAL | Impacted: Self-hosted GitLab CE/EE deployments, Software development teams, Organizations relying on public GitLab projects

Summary: GitLab has released security updates to address a critical vulnerability impacting its Community Edition (CE) and Enterprise Edition (EE) software that, under certain conditions, could allow an unauthenticated attacker to remotely modify or delete public projects and user data. The flaw, tracked as CVE-2026-19478, has been rated Critical by GitLab and assigned a CVSS score of 9.4. Released on…

Why it matters: Unauthenticated attackers may be able to destroy or manipulate public development assets, risking both direct data loss and broad disruption of collaborative workflows.

Practitioner Perspective

Any internet-accessible GitLab instance is now a high priority target, given the criticality and lack of required authentication for exploitation of CVE-2026-19478. Attackers could irreversibly delete source code or data, disrupting business operations or supply chains. Automated mass scanning is highly probable, which increases the urgency for emergency patching. Security teams must recognize that backups alone are inadequate without ensuring recovery processes for compromised public projects. Defensive focus should be on immediate patch rollouts and visibility into recent public project changes for evidence of tampering.

Recommended Actions

• Patch all GitLab CE/EE instances to address CVE-2026-19478 immediately, prioritizing any internet-exposed deployments
• Review recent audit logs for mass deletion or modification events in public repositories from unauthenticated sources

Snowflake GitHub Actions Flaw Lets Crafted Issues Trigger Command Injection

Source: The Hacker News | Risk: HIGH | Impacted: GitHub-based CI/CD projects, Organizations integrating Snowflake and Jira, Developers using open source Snowflake connectors

Summary: Cybersecurity researchers at Wiz have disclosed a new GitHub Actions workflow injection vulnerability in Snowflake’s public snowflakedb/snowflake-connector-net repository that it said could be exploited through a crafted GitHub issue to execute commands in a workflow containing internal Jira credentials. The issue was present in .github/workflows/jira_issue.yml, which ran when a…

Why it matters: Workflow injection in public repositories can lead to unintended leakage or misuse of sensitive internal credentials, especially when automation bridges between cloud services and enterprise platforms.

Practitioner Perspective

Security engineers managing SaaS integrations and CI/CD pipelines must treat workflow triggers as potential attack vectors, particularly in environments like the Snowflake Connector’s public repo with tied-in Jira credentials. Malicious actors abusing issue creation can execute arbitrary commands and potentially exfiltrate secrets. This threat underscores the need to limit credential exposure and harden automation against unsolicited user input. Defenders should re-assess what secrets are exposed in automated workflows and whether workflow files use proper security context boundaries. Immediate mitigation is essential because similar patterns exist broadly across open source and enterprise repos.

Recommended Actions

• Audit .github/workflows/jira_issue.yml or similar workflow files for unsafe context handling and public triggers
• Rotate any internal Jira or Snowflake credentials exposed via GitHub Actions in public repositories

Forminator WordPress Flaw Can Enable Unauthenticated RCE via Malicious PHP Uploads

Source: The Hacker News | Risk: CRITICAL | Impacted: WordPress administrators, Sites using Forminator Forms, Shared web hosting providers

Summary: A critical security flaw has been disclosed in Forminator Forms, a WordPress plugin with more than 600,000 active installations, that could be exploited to achieve arbitrary code execution on susceptible sites. The vulnerability, tracked as CVE-2026-15748, is rated 9.8 out of 10.0 on the CVSS scoring system. It was discovered and reported by a security researcher who goes by the…

Why it matters: Widespread RCE in a high-install base WordPress plugin enables trivial compromise of websites, potentially escalating to larger breaches or persistence across customer environments.

Practitioner Perspective

Any website running Forminator Forms is especially vulnerable to commodity exploitation. Attacks exploiting CVE-2026-15748 can be rapidly automated, delivering remote code execution via malicious PHP uploads to unauthenticated endpoints. Webmasters and security admins must act before attackers weaponize this in massive botnet campaigns. Typical detections based on WAF signatures or basic file uploads may be evaded, ensure security controls are plugin-aware. The crucial takeaway is to prioritize plugins with large user bases for ongoing monitoring and response.

Recommended Actions

• Deploy patch for CVE-2026-15748 on all WordPress sites running Forminator Forms
• Hunt for suspicious PHP file uploads and newly created scripts in webroot

Cavern C2 Uses DNS and Google Apps Script to Blend Into Legitimate Traffic

Source: The Hacker News | Risk: HIGH | Impacted: Enterprises using Google Workspace, Organizations operating in regions targeted by Iranian APTs, Security operations with limited DNS and SaaS visibility

Summary: Cybersecurity researchers have traced the continued evolution of the Cavern (aka Cav3rn) command-and-control (C2) framework used by Iranian nation-state hackers in attacks targeting entities in Israel. Russian cybersecurity company Kaspersky said its ongoing monitoring of the threat activity cluster since December 2025 has led to the discovery of previously unreported components that expand the…

Why it matters: Nation-state threat actors are adapting command and control to leverage ubiquitous cloud services and DNS tunneling, making detection and interdiction far more difficult for defenders inspecting standard traffic.

Practitioner Perspective

The Cavern C2 framework exemplifies the ongoing shift by APTs to blend C2 traffic with sanctioned tools, specifically, using Google Apps Script and DNS protocols to evade perimeter inspection. Traditional signature-based controls and blocklists will struggle against this approach, especially for organizations where DNS and Google services are mission-critical. Network defenders should treat unexpected or high-frequency Google Apps Script and suspicious DNS traffic as a hunting priority. This is a strong reminder to baseline normal cloud and SaaS behavior and alert on small anomalies that indicate advanced tradecraft. Modern C2 blending requires defenders to close the gap between permitted workflows and active threat detection.

Recommended Actions

• Monitor DNS logs for anomalous query volumes and potential command-and-control patterns attributable to Cavern C2 usage
• Inspect Google Apps Script API activity originating from endpoints outside documented business runbooks

How MCP Servers Can Expose Enterprise Secrets

Source: The Hacker News | Risk: HIGH | Impacted: Organizations deploying MCP or similar AI agents, IT and DevOps teams integrating AI into production services, Security teams with limited AI infrastructure visibility

Summary: MCP servers can expose enterprise secrets through plaintext configuration files, over-permissioned access and prompt injection, often before security teams even know the server is running. As more organizations adopt AI agents into their systems, that exposure can silently become a major gap in MCP server security. The Model Context Protocol (MCP) allows AI agents to reach the tools and data…

Why it matters: Poorly secured AI agent infrastructure can expose sensitive configurations and secrets before defenders notice, amplifying the risk from both internal misuse and external exploitation.

Practitioner Perspective

Organizations rapidly integrating AI via MCP servers face a hidden risk: secrets and credentials stored in plain text or with overly broad permissions provide attackers, manual or automated, direct access to company data. The Model Context Protocol extends agents’ reach and, without precise security controls, may create an unmonitored shadow IT foothold. As usage expands, standard monitoring or IAM policies may not catch prompt injection, configuration leaks, or privilege creep. Security teams need to make AI agent infrastructure part of standard audit and incident response. The key lesson: treat new AI control layers with the same scrutiny as any externally reachable platform.

Recommended Actions

• Audit all MCP server configurations for plaintext credentials and remove any unnecessary secrets
• Review IAM policies and restrict MCP server permissions to minimum required access

What We’re Watching

• Monitoring for active exploitation of CVE-2026-19478 (GitLab, CVSS 9.4) and CVE-2026-15748 (Forminator, CVSS 9.8), with rapid mass scanning likely this week.
• Further developments on exploitation of VMware vCenter (CVE-2026-59310, CVSS 9.8) by China-nexus groups; watch for additional ransomware payloads.
• Expansion of Cavern C2 activity leveraging DNS and Google Apps Script, especially targeting EMEA enterprise networks.
• Unisoc Android exploit chain remains unpatched; risk is rising for telecoms and IoT device fleets.
• Signs of cross-SaaS credential abuse or workflow injection beyond current Snowflake and CI/CD disclosures.

Categories: Cybersecurity Blog, Cybersecurity News

Tags: Cavern C2, Credential Compromise, CVE-2026-19478, Evooo1Bot, Forminator, GitLab, SaaS Security, Snowflake, Tax Breach, Unisoc, VMware, WordPress