Last updated: October 5, 2026 at 10:28 AM UTC
All 897 Vulnerability 362 Breach 144 Threat 384 Defense 7

Self-spreading prompts can jump between AI agents through shared state files

Researchers, including teams at Anthropic and EPFL, demonstrated that self-propagating instructions can spread from one AI agent to another through the editable prompt and state files that autonomous agent harnesses use to carry context between sessions. In simulated multi-agent coding setups, a payload written into a shared file could infect the next agent that read it. The researchers call the risk real but currently limited, noting there is no sign of it spreading in the wild and that compromising one agent usually already grants machine access. Encouragingly, adding a single short warning paragraph to an agent's system prompt cut propagation to nearly zero across the payloads they tested.

Check
If you run autonomous or multi-agent setups, treat their persistent prompt and state files as an integrity boundary, and review what those files contain and which agents can write to them.
Affected
Autonomous and multi-agent systems that share editable prompt or state files between agents or sessions; a malicious instruction written into such a file can propagate to other agents that read it.
Fix
Control and review writes to shared agent state, add a system-prompt warning that cut propagation to near zero in testing, isolate agents and their files, and monitor state files for unexpected instructions.

Sixteen typosquatted RubyGems packages steal browser logins and crypto wallets

Researchers flagged a typosquatting campaign, tracked as StubMaker, that planted sixteen malicious packages on RubyGems to deliver a Windows information stealer. The packages imitate popular Ruby dependencies with clumsy misspellings, betting that a developer will mistype a name during installation. Once installed, the malware harvests browser credentials, cryptocurrency wallets and seed phrases, and Telegram data from the developer's machine. The campaign's name refers to its trick of faking a build toolchain so a malicious install looks like a routine one. It is the latest reminder that open-source package registries remain an easy delivery route for stealers aimed at developers.

Check
Double-check RubyGems dependency names before installing, watch for clumsy misspellings of popular gems, and scan developer machines and CI for the malicious packages if you use Ruby.
Affected
Ruby developers who mistype or fail to verify gem names during installation; the malicious packages install a Windows stealer that takes browser logins, cryptocurrency wallets and seed phrases, and Telegram data.
Fix
Pin and verify dependency names and sources, use lockfiles, prefer tooling that flags typosquats, rotate credentials and wallets on any machine that installed a bad gem, and keep wallets off dev machines.

Critical GitLab flaw lets unauthenticated attackers delete public projects and data

GitLab shipped an out-of-band critical patch for a flaw that lets an unauthenticated attacker remotely modify or delete public projects and user data through a GraphQL directive. Tracked as CVE-2026-19478 and scored 9.4, it affects self-managed Community and Enterprise installations; GitLab.com and Dedicated are already fixed. The company released it outside its normal twice-monthly schedule, and the fixed versions are 19.2.4, 19.1.6, 19.0.8, and 18.11.11, with the 18.2 through 18.10 branches left in the affected range and needing an upgrade. A second, lower-severity GraphQL flaw involving cross-site request forgery was fixed in the same release. GitLab reports no known exploitation yet.

Check
Upgrade self-managed GitLab to a fixed release immediately, and if you run a version between 18.2 and 18.10, plan an upgrade since those branches did not receive a backported fix.
Affected
Organizations running self-managed GitLab Community or Enterprise Edition (CVE-2026-19478); an unauthenticated attacker can remotely modify or delete public projects and user data through a GraphQL directive.
Fix
Apply the out-of-band patch now, prioritize internet-reachable instances, review logs for unexpected GraphQL activity and project or user changes, and restore any affected projects from backups if tampering is found.

Unauthenticated Forminator flaw lets attackers upload PHP and take over WordPress sites

A critical flaw in Forminator Forms, a WordPress plugin with more than 600,000 installations, lets unauthenticated attackers upload executable PHP files and take over a site. Tracked as CVE-2026-15748 and scored 9.8, the bug chains weaknesses in the plugin's upload handling: an attacker smuggles a forged record through a Select field that declares itself a file upload, then slips a PHP file past a blocklist that only checks exact extensions. Exploitation requires a form with both a file upload field and a select field, and it affects all versions up to 1.56.1. Because it needs no authentication, automated scanners can hunt for vulnerable sites at scale.

Check
Update the Forminator plugin to a version newer than 1.56.1 across all WordPress sites, and check for unexpected PHP files in upload directories and unfamiliar administrator activity.
Affected
WordPress sites running Forminator 1.56.1 or earlier with a form containing both a file upload and a select field (CVE-2026-15748); an unauthenticated attacker can upload PHP and fully compromise the site.
Fix
Patch the plugin, put a web application firewall in front of the site, scan for web shells and unauthorized files, and remove or reconfigure vulnerable forms until the update is applied.

Unisoc modem exploit chain reaches the Android kernel through a video call

Researchers at SSD Secure Disclosure published a two-stage exploit chain that gains full Android kernel access on devices using Unisoc modem firmware, triggered by a VoLTE video call. The first stage, disclosed earlier this year, is remote code execution in the modem via a malformed call; the new second stage abuses a memory-isolation weakness in the modem to disable its protections and reach kernel memory. Pulling it off requires the attacker to run a rogue 4G network and the victim to answer the call. The affected firmware is shared across several Unisoc chipsets used in budget phones from brands like Motorola, Realme, and Xiaomi, and there is no fix from the chipmaker.

Check
Identify devices using affected Unisoc chipsets in your fleet, and since there is no vendor patch, watch for manufacturer firmware updates and weigh the risk for devices on untrusted cellular networks.
Affected
Android devices built on affected Unisoc chipsets, common in budget phones and some embedded and vehicle systems; an attacker on a rogue network can chain a video call into kernel access.
Fix
Press device makers for firmware updates, treat the modem as an untrusted boundary in device designs, and restrict exposure to rogue cellular networks where possible, since the attack needs an answered call.

GitHub issue title let an AI agent hijack Snowflake CI and steal a token

Researchers at Wiz found that a public Snowflake code repository could be hijacked through nothing more than a crafted GitHub issue title. A workflow that ran when issues were opened dropped the attacker-controlled title straight into a command, so an unauthenticated user could run code on the GitHub Actions runner and steal a Jira API token used by the automation. The notable twist is how the bug arrived: it was introduced days earlier by an AI tool meant to fix security issues, and an AI code reviewer approved the change. Snowflake fixed it by passing the title safely as an argument rather than expanding it into a command.

Check
Audit GitHub Actions workflows that run on untrusted input like issue titles or pull requests, and never interpolate that input directly into shell commands; pass it as environment variables or arguments.
Affected
Repositories whose workflows trigger on issues or pull requests and interpolate attacker-controlled text into commands; an unauthenticated user can run code on the runner and steal the secrets the workflow holds.
Fix
Sanitize untrusted workflow input, minimize the secrets and permissions each workflow can access, and do not assume AI-generated or AI-reviewed code is safe, since automated fixes and reviews miss injection flaws.

South Carolina loan company breach exposes Social Security numbers of 750,000

A South Carolina loan company disclosed a data breach that exposed the financial information and Social Security numbers of nearly 750,000 people. According to reporting, the breach affects anyone who received a loan through the company or who inquired about a loan product through a third party, meaning the exposure reaches beyond direct customers. Social Security numbers combined with financial details are among the most useful data for identity theft and fraud, and such records frequently end up for sale on criminal marketplaces. Lending and debt-related companies remain a favored target because they concentrate exactly this kind of sensitive financial and identity data.

Check
Anyone who took out or inquired about a loan through the affected company should watch for identity-theft signs, consider a credit freeze, and beware fraud referencing their financial details.
Affected
Nearly 750,000 people who obtained or inquired about a loan through the company, including via third parties; their Social Security numbers and financial information were exposed, raising identity-theft risk.
Fix
Affected people should freeze credit and monitor accounts; organizations holding financial and identity data should minimize what they retain, control access tightly, and extend protections to third-party partners.

Critical SAP Commerce Cloud flaw exploited days after patch with no public exploit

Attackers began exploiting a critical SAP Commerce Cloud flaw within days of its patch, even though no public proof-of-concept exists. Tracked as CVE-2026-58231 and scored 10.0, the improper-authorization bug in the Data Hub Adapter lets an unauthenticated attacker abuse a default authentication client and send crafted input to reach arbitrary code execution. Threat intelligence firm Defused saw the first exploitation attempts hit its honeypots three days after SAP's August patch, classified as automated mass scanning of internet-facing deployments. Shadowserver tracks more than 4,200 exposed SAP Commerce Cloud systems, mostly in Europe and North America. Prior critical SAP flaws have been used by state actors and ransomware crews.

Check
Apply SAP's August patch for Commerce Cloud immediately per Security Note 3771065, then re-deploy the updated version, and prioritize any internet-facing or hybrid deployment as an emergency.
Affected
Organizations running unpatched SAP Commerce Cloud (CVE-2026-58231); an unauthenticated attacker can reach arbitrary code execution with low complexity, and exploitation is already underway despite no public exploit code.
Fix
Patch and re-deploy now, restrict access to Commerce Cloud from untrusted networks, review the Data Hub Adapter and application logs for suspicious requests and code execution, and monitor for follow-on compromise.

Exploited macOS Screen Sharing flaw gives attackers root to plant miners

The Netherlands cyber agency warned that attackers are exploiting a recently patched macOS flaw to gain root on internet-exposed Macs and install cryptocurrency miners. Tracked as CVE-2026-65400 and scored 9.8, the authentication flaw in the Screen Sharing component lets a network attacker authenticate to the built-in remote desktop service, which uses VNC on port 5900, without valid credentials due to flawed state management. Apple fixed it in emergency updates on August 6 for macOS Tahoe, Sequoia, and Sonoma. Screen Sharing is off by default, but any Mac with it enabled and reachable from the internet is at high risk, and several have already been compromised to run Monero miners.

Check
Install Apple's August macOS updates on all Macs, and confirm Screen Sharing is disabled or that port 5900 is not reachable from the internet on any system where remote desktop is enabled.
Affected
Macs with Screen Sharing enabled and reachable from the internet on unpatched macOS Tahoe, Sequoia, or Sonoma (CVE-2026-65400); a network attacker can authenticate without credentials and gain root.
Fix
Update macOS, disable Screen Sharing where it is not needed, restrict remote desktop access to trusted networks or a VPN, and check exposed Macs for unauthorized access and cryptominer processes.

Unpatched GeoServer zero-day allowing code execution is already being probed

A newly disclosed zero-day in GeoServer, the widely used open-source geospatial server, is already drawing exploitation attempts, according to watchTowr. The flaw is a SQL injection issue that can lead to remote code execution, and it remains unpatched, with no CVE assigned yet. It was first disclosed publicly by a researcher on August 12, and attackers commonly begin probing internet-facing servers as soon as such details appear. GeoServer instances are frequently exposed to the internet to serve mapping and location data, which makes an unpatched code-execution flaw in the platform an attractive and reachable target. Defenders should treat exposed instances as at risk until a fix ships.

Check
Identify internet-facing GeoServer instances, restrict access to them, and monitor closely for exploitation, since the flaw is unpatched and attackers are already probing for vulnerable servers.
Affected
Organizations running internet-exposed GeoServer; an unpatched SQL injection flaw can lead to remote code execution, there is no fix or CVE yet, and probing for vulnerable instances has already started.
Fix
Limit GeoServer exposure behind authentication or a firewall until a patch is available, monitor for suspicious database queries and process execution, and apply the vendor fix as soon as it is released.