10/14/2026-10/21/2026 Next.js Ships Out-of-Band Patch; PHP2Shell: Mass Exploitation Looms for Leaked Critical PHP Flaws; OpenCode Security Breach And More.

1. Next.js Ships Out-of-Band Patch for Two Critical RCE Flaws in Caching and SVG Processing

Next.js released an out-of-band security update on October 14, fixing two critical unauthenticated remote code execution (RCE) flaws and one high-severity denial-of-service (DoS) flaw. Fixes are in versions 16.4.1 and 15.5.28.

The flaws:

• use cache RCE (CVSS 9.5): Affects version 16 apps with Cache Components enabled, where a use cache function returns multiple typed arrays. It’s far narrower than December 2025’s React2Shell.
• SVG RCE (CVE-2026-96889, CVSS 9.5): A librsvg memory bug reached through sharp. It affects apps passing attacker-supplied SVGs on glibc-based Linux, including next/og on Node.js.
• Server Actions DoS: Crafted requests can max out a server process’s CPU in App Router apps with at least one Server Action.

What to do:
Upgrade to 16.4.1 or 15.5.28, then rebuild and redeploy. Version 16.4.1 requires sharp 0.35.5, but 15.5.28 may keep an older, vulnerable sharp. Check with npm ls sharp and update if needed. Without upgrading, you can mitigate the SVG flaw by updating sharp or blocking SVG rendering. The other two flaws have no workaround.

Scanners may miss the use cache and Server Actions flaws, which had no CVE or npm advisory as of October 15. No attacks have been reported.

2. PHP2Shell: Mass Exploitation Looms for Leaked Critical PHP Flaws

Details of two critical PHP vulnerabilities, dubbed PHP2Shell, have leaked online ahead of coordinated disclosure and official patches. Both carry a CVSS score of 9.2.
PHP has scheduled patches for Wednesday, 21 October 2026 and urged users to prepare for immediate upgrades. It warned that fixes may come sooner if technical details are published or in-the-wild exploitation emerges.

The flaws, reportedly CVE-2026-109618 and CVE-2026-109619, could allow remote code execution. Given their scores, CERT-EU says both are likely exploitable without authentication. Public reporting suggests all versions from PHP 5 onwards are affected, and one report describes the first flaw as a use-after-free bug. The root cause, affected component, and attack path remain undisclosed.

WatchTowr says it reproduced CVE-2026-109618 but is withholding details until patches ship. Both WatchTowr and Huntress report no exploitation in the wild so far.

3. OpenCode Security Breach Exposes Third-Party API Keys of its Console Users

OpenCode disclosed a security breach affecting 1.4% of its Console users (not its entire user base). Third-party API keys saved in affected workspaces, including those for OpenAI and Anthropic, may have been exposed. In an October 17 statement, the company linked the incident to a large-scale distillation attack and said it was working with Anthropic, OpenAI, and Google. Affected users were emailed that morning; those who received no email were not impacted.

According to the notification, attackers gained unauthorized access to a legacy system that OpenCode was already preparing to shut down. The wording describes possible exposure, not confirmed theft or use of every key.

Affected users should revoke and replace keys through each provider’s dashboard, update every application using them, and review recent usage and billing for unexpected activity.

Distillation means training one AI model on another’s outputs. OpenCode has not explained how attackers got in, how long they stayed, how many keys were involved, or whether stolen credentials were used for the distillation requests. It also named no attacker and reported no confirmed loss figure.

The incident was still ongoing at publication, and OpenCode said it could not share more details.

4. Popular WordPress SEO Plugin Rank Math PRO Hijacked to Deliver Self-Restoring Backdoor

Rank Math PRO copies downloaded from rankmath.com or delivered as updates contained malware, according to a company notice. The affected version was 3.0.123, but version number alone doesn’t show exposure: only copies obtained during that window are affected. The free WordPress.org plugin isn’t named.
Sites that installed and activated an affected copy should be treated as compromised, even if later updated to clean version 3.0.124. The malware can recreate a hidden backdoor, and may have added backdoor files, administrator accounts, scheduled tasks, SSH keys, and .htaccess changes. Any credentials the site could reach should be considered exposed. Wordfence rates the incident (CVE-2026-111862) 9.8.

Recovery:
Restoring a pre-20:02 UTC October 15 backup is preferred, followed by a security scan and changing all credentials. Without a clean backup, first delete the entire rank-math-pro folder, remove three malicious wp_options entries, and block rank1cdn[.]com. Then hunt for rogue files, admin accounts (wpsupport_), and server persistence. Change all credentials, and install 3.0.124 last, directly from rankmath.com.

Rank Math hasn’t explained how the files entered its system or how many customers were affected. This is at least the third premium WordPress plugin update-channel compromise this year.

5. CVE-2026-99999: Critical PwnEscape Linux Kernel Flaw Enables Guest-to-Host Escape

CVE-2026-99999 (“PwnEscape”) is a Linux kernel flaw, present since version 2.6.27, that lets a guest VM break out to the host. Malformed checksum metadata can make skb_checksum_help() alter an IPv4 header after it was validated. Researchers used this to change a 20-byte header into a 60-byte one, leaking 32 bytes of host memory. It scores CVSS 9.3 (Critical) with a Local attack vector, since the attacker needs code execution inside a guest.

In a controlled KVM environment, researchers chained the leak into host-kernel writes and root execution. Only the memory disclosure was reproduced on Vercel’s live sandbox infrastructure, with no evidence of customer data exposure. Multi-tenant platforms running untrusted code are most at risk. No exploitation or CISA KEV listing has been reported.

Mitigation:
Upgrade the host kernel (guest updates don’t help) to a fixed stable release, such as 5.10.272, 5.15.223, 6.1.190, 6.6.159, 6.12.113, 6.18.57 or 7.2.11. Check distribution advisories, since fixes may be backported. Reboot, then verify the active kernel on every host. Monitor for host crashes and anomalous fragmentation tied to guest traffic. If an escape is suspected, treat the host as compromised.

10/07/2026-10/14/2026 GhostAction Attack Compromises 500+ GitHub Accounts; Docker Fixes Critical Two-Year-Old Hub Flaw; Critical Code Injection and Memory Corruption Vulnerabilities And More.

1. GitHub Tightens npm Publishing After Flaw Left 1,500+ Packages Vulnerable to Hijacking

GitHub now expires unvalidated npm trusted publishing configurations 48 hours after creation, after Bloom Security found attackers could push new versions of others’ packages without stealing credentials. A configuration becomes validated after its first successful publish; changing the repository or project identity requires a new 48-hour window. npm also rejects trusted publishing tokens from GitHub Actions issue_comment events.

The flaw, dubbed SlugFest, stems from npm anchoring trust to a repository’s name (“owner/repository”) rather than its immutable ID until the first publish. If a maintainer renames, transfers or deletes a repository, an attacker can claim the freed name, mint an OIDC token, and obtain a publish credential for the victim’s package, inheriting its reputation and downloads. Bloom found over 1,500 vulnerable packages with more than 10 million combined downloads; AI agents pulling latest versions could worsen exposure. Maintainers should audit trusted publisher bindings, recreate them after renames or transfers, delete them when repositories are removed, and monitor unexpected publishes.

2. GhostAction Attack Compromises 500+ GitHub Accounts to Steal Cloud and AI Credentials 

A new GhostAction campaign has compromised over 500 GitHub accounts and, since October 7, 2026, spread malicious workflows across tens of thousands of repositories. It steals GitHub Actions secrets and searches source code and Git history for cloud and AI credentials.

An October 8 burst involved compromised maintainer accounts henrywoo and kitao, which injected security-audit.yml into 346 repositories, including uber/athenadriver and kitao/pyxel. The workflow runs on every push and manual dispatch, targeting secrets whose names were extracted from existing workflows. No malicious package releases had been found as of October 9.

The workflow also checks out full history and scans git log -p --all output for 13 credential patterns covering AWS, Anthropic, OpenAI, GitHub and others. Results go via cleartext HTTP POST to 193.32.204[.]199, even when nothing is found. Socket advises removing injected workflows, rotating all exposed credentials (not just Actions secrets), revoking sessions and tokens, scanning history, reviewing CloudTrail, and blocking the IP.

3. Docker Fixes Critical Two-Year-Old Hub Flaw That Let One User Push Images as Another

A flaw in Docker Hub (CVE-2026-105445, CVSS 9.4) let one user push, pull or delete images as another. Docker fixed it on September 30 and found no evidence of exploitation.

The bug sat in the feature converting a personal account into an organization. Conversion transferred the account’s personal access tokens to the designated owner, but the token secrets stayed unchanged. An attacker could create a token, convert the account, name a victim as owner, and use the token as that victim, without the victim’s consent or notification.

Researchers Peter Molnar and Krisztian Hozak, who named it GhostPat, reported it; Docker fixed it within four hours. The flaw had been open since August 2024.

Docker reviewed about 304,000 pushes with transferred tokens and found no malicious activity, but treated all transferred tokens as possibly affected, since logs miss unused ones. Affected users were emailed October 2. Users should review tokens, revoke unfamiliar ones, and use organization access tokens for automation.

4. SAP Security Update Patches Critical Code Injection and Memory Corruption Vulnerabilities

SAP’s October 13, 2026 Patch Day fixes 22 entries: four critical, three high, 14 medium and one low, covering S/4HANA, NetWeaver, Web Dispatcher, Commerce Cloud and development libraries.

The top-rated flaw, CVE-2026-89111 (CVSS 10.0), is an OAuth2 server-side request forgery in SAP Cloud SDK for Python before 0.45.2. In multi-tenant BTP applications, an attacker controlling the tenant_subdomain parameter can redirect token requests and expose client credentials.

CVE-2026-89107 (9.9) lets an authenticated attacker with specific business privileges inject executable ABAP code through S/4HANA’s Manage Substitution/Validation Rules (Note 3805589). CVE-2026-89110 (9.9), a broken access control flaw in NetWeaver Visual Composer 7.50, and CVE-2026-89108 (9.1), a missing authorization check in Manufacturing Integration and Intelligence, are also critical.

CVE-2026-58249 (7.5) is a high-severity memory corruption bug in the Internet Communication Manager that lets unauthenticated remote attackers crash processes, with no confidentiality or integrity impact.

No exploitation of these flaws has been reported. SAP urges prioritized patching; administrators should check installed components against the full affected-version lists.

5. GitLab Patches Max-Severity Vulnerability CVE-2026-97229

GitLab has fixed CVE-2026-97229 (CVSS 10.0), a critical integer overflow in Community and Enterprise Editions that could let unauthenticated attackers execute code on servers. The cause is weak validation of regular expressions in CI/CD configurations. Affected versions are 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2; users should upgrade. Researcher joaxcar reported it via HackerOne.
GitLab also patched three high-severity flaws:

• CVE-2026-92883 (8.7): a crafted repository can make another user’s browser run malicious JavaScript.
• CVE-2026-16301 (8.5): Developer-role users can bypass permissions and run pipelines on protected branches.
• CVE-2026-14814 (8.2): a pattern-matching flaw lets attackers manipulate cached files, so victims’ pipelines run malicious code and may leak environment variables.

In early October, GitLab fixed CVE-2026-90970 (9.9) in its AI Gateway. An authenticated user with Duo Agent Platform access could escape the prompt template sandbox via a crafted flow configuration and run commands on the gateway host. Fixed versions are 19.2.4, 19.3.2 and 19.4.1.

6. Anthropic Launches Free AI Vulnerability Scanner for Open-Source Projects

Anthropic has launched OSS Scanner, an opt-in, free AI vulnerability scanner for open-source projects, drawing on its Project Glasswing experience. Its strongest models, including Claude Mythos, will run periodic scans, and the reports are fully model-generated, with no human review or triage.

Anthropic expects to select projects using criteria similar to Google’s OSS-Fuzz. Core maintainers enroll by opening a pull request to the OSS Scanner GitHub repository with a YAML file giving the repository link, a primary contact email, and a Dockerfile path that builds the project with all dependencies so an offline agent can audit it. Optional fields include CC emails, a GPG key, a threat model file, and an opt-out flag. So far, 116 pull requests have been submitted.

Because of possible false positives, Anthropic imposes no 90-day disclosure period, though manually validated reports may follow its CVD policy.

Anthropic has identified over 29,000 candidate vulnerabilities, reported about 6,000, and produced 584 advisories as of October 2. It also announced a Critical Infrastructure Defense Program.

09/30/2026-10/07/2026 Critical Atlassian Flaw; WordPress Malware Comes Back After Removal; GitLab Patches Critical AI Gateway Flaw And More.

1. Critical Atlassian Flaw Lets Unauthenticated Attackers Read Known Files Across 8 Products

A critical flaw (CVE-2026-21589, CVSS 9.3) in eight self-hosted Atlassian Data Center products lets unauthenticated attackers read files in the web application root directory. Attackers must already know a file’s exact name and path. Atlassian disclosed it on October 5 and listed fixed versions per product. Cloud products are already patched.

Atlassian advises upgrading to a fixed LTS version or later, including for end-of-life releases. If that isn’t possible immediately, take the instance offline or restrict external access. Temporary mitigations block URLs with “..” next to “/”, “” or “::”, including encoded forms, via a WAF or reverse proxy, a Tomcat RewriteValve rule, or urlrewrite.xml (Bitbucket). Atlassian calls these limited and no replacement for patching.

Details are inconsistent: the Crowd and Bamboo fixed versions differ between the advisory and the CVE record. Server editions are listed as affected with no fixes.
Atlassian found no exploitation in cloud, but can’t confirm for self-hosted instances. Teams should search access logs for traversal patterns. A similar Jira flaw (CVE-2021-26086) was later exploited.

2. WordPress Malware Comes Back After Removal Using a Self-Healing Backdoor

A WordPress backdoor called SC, documented by Sucuri on September 30, 2026, restores deleted malware within seconds by spreading its components across website files, the database, and server memory. The report doesn’t establish the original entry point or how many sites are affected.

SC occupies at least eight locations. A configuration directive launches a loader before ordinary PHP requests, and the loader rebuilds a fake caching plugin from copies, encoded backups, or recovery archives. Early-loading components and an injected theme block provide further recovery routes. The backdoor hides from plugin lists and update checks, conceals an administrator account, and can forge authentication cookies. For commands, it queries smart contracts through about twenty public Ethereum gateways, so blocking one route doesn’t help. Replies can deliver PHP, browser scripts, or orders to delete security plugins.

Sucuri advises neutralizing the loader target first, then removing the directive. Next come database payloads, shared memory copies, scheduled tasks, triggers, and hidden admins, then all files in one pass. Finish by closing the entry point and rotating credentials.

3. LibreOffice and OpenOffice Flaws Let Malicious Spreadsheets Run Code Without Macro Warnings

Researchers have shown that a malicious spreadsheet can make LibreOffice and Apache OpenOffice run attacker code the moment it’s opened, with no macro-style warning. It works only when Java support is enabled, and so far exists only as a proof of concept, with no reported real-world use.

The attack chains normal features: a spreadsheet’s auto-refreshing “database range” fetches an ODB file from a web address, which names a JDBC driver hosted in a remote JAR file. The program downloads and starts it, running the attacker’s code without ever asking the user to trust the document. Researchers tested it on Windows and Linux.

LibreOffice fixed CVE-2026-63277 on October 5; users should update to 26.2.5 or 26.8.0. Apache OpenOffice (CVE-2026-59265) remains unpatched through version 4.1.16, with a fix expected in 4.1.17. Until then, disable Java or avoid opening untrusted spreadsheets.

4. GitLab Patches Critical AI Gateway Flaw Allowing Arbitrary Command Execution

GitLab has patched CVE-2026-90970 (CVSS 9.9), a critical flaw in its AI Gateway that lets authenticated users run arbitrary commands on self-hosted deployments. It affects versions from 18.1.6 up to, but excluding, 19.2.4, plus the 19.3 branch before 19.3.2 and the 19.4 branch before 19.4.1.

The bug is an improper neutralization issue in the custom-flow prompt template mechanism. A user with Duo Agent Platform access can submit a crafted flow configuration, escape the template sandbox, and execute commands on the gateway host or container.

Fixed releases are 19.2.4, 19.3.2, and 19.4.1. GitLab lists no workaround, so upgrading is the main mitigation. Because the AI Gateway is separate from the core application, administrators should check the gateway image or Helm configuration rather than assume a GitLab CE/EE upgrade covers it. Teams should also restrict flow-configuration access and review recent templates for unexpected changes.
GitLab.com, Dedicated, and instances using a GitLab-hosted gateway need no action.

5. 100+ Compromised Websites Use Fake Cloudflare Checks to Deliver LunexStealer

CERT-UA has identified over 100 websites compromised in September 2026 with malicious JavaScript that serves LunexStealer, a campaign attributed to the cluster UAC-0277. Visitors see a fake Cloudflare verification page that tricks them into running a command (ClickFix), which installs a malicious MSI package. The script retrieves its settings from a Polygon or Ethereum smart contract (EtherHiding), and the lure is shown only to Windows users arriving from search results.

Three MSI variants exist: a basic installer; one that bypasses UAC, sets Defender exclusions and abuses a vulnerable AMD driver to blind security tools; and one that uses DLL sideloading.

LunexStealer also installs a browser extension, LUNARAXE, posing as “Microsoft Office Word Editor”. It steals cookies, history and credentials, strips CSP headers and can run arbitrary JavaScript. The NAIVEMESS component gives it file system access.
CERT-UA advises blocking the Run dialog, restricting MSI installs, monitoring msiexec.exe, enabling Microsoft’s vulnerable driver blocklist, and allowlisting browser extensions.