Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7
Tag: code-execution (14 articles)Clear

Brotli decoder memory corruption flaw exposes Node.js, Bun, Python, and many other programs to code execution

OpenAI's Codex Security team reported CVE-2026-111497, a memory corruption flaw in Google's Brotli decoder that Google rates 9.2, where crafted compressed data overwrites past a buffer and can crash, leak memory, or run attacker code. Because the vulnerable C code is bundled widely, every program shipping it inherits the bug, including Node.js, Bun, .NET, Envoy, Istio, Python Brotli bindings, the Ruby gem, and others, with FFmpeg, ClickHouse, and Apache Arrow also affected. Each project needs its own update, such as Node.js 24.22.1 or Bun 1.4.4. Imperva demonstrated code execution on Node.js 24, calling it Node2Shell, but no in-the-wild exploitation is reported.

Check
Inventory software that decodes Brotli, including Node.js, Bun, .NET, Envoy, Istio, and Python bindings, and apply each project's fixed version.
Affected
Programs bundling the vulnerable Brotli decoder can be crashed or driven to code execution by crafted compressed data, regardless of the application's own code.
Fix
Update every affected runtime and library to its patched release, prioritize internet-facing services that accept Brotli-compressed input, and track fixes for FFmpeg and others still pending.

LibreOffice and OpenOffice flaws let malicious spreadsheets run code without macro warnings

Researchers disclosed CVE-2026-63277 in LibreOffice and CVE-2026-59265 in Apache OpenOffice, flaws that let a malicious spreadsheet run code without triggering macro warnings. The attack chains legitimate features: a spreadsheet defines a database range that downloads an ODB database file from a web address, and that file references a JDBC driver, causing automatic download and execution of attacker-controlled Java code. LibreOffice fixed the issue in versions 26.2.5 and 26.8.0 on October 5, while Apache OpenOffice remains affected through 4.1.16 with 4.1.17 still in testing. The technique exists only as a proof of concept, credited to researchers at V12 and Codean Labs.

Check
Upgrade LibreOffice to 26.2.5 or 26.8.0, and for Apache OpenOffice avoid opening untrusted spreadsheets until 4.1.17 ships, disabling automatic database and JDBC features.
Affected
Vulnerable LibreOffice and OpenOffice versions let a crafted spreadsheet download a database file and JDBC driver that runs attacker Java code without any macro warning.
Fix
Apply the LibreOffice fixes, restrict or disable JDBC and external database connections, and treat spreadsheets from untrusted sources as potentially executable content.

WordPress flaw forces theme installs and can chain to server code execution

WordPress shipped 7.1.1 on September 17 to fix a flaw that pwn.ai calls Click2Shell, where a crafted link opened by a logged-in administrator installs a theme from the official directory with no click. Two parts of WordPress read the link differently, so attacker-added characters steer the admin browser into clicking Install, and the logged-in session supplies the permission and security token. Alone it only installs a real, switched-off theme, but the researchers chained it with a second flaw in the Mobile Repair Zone theme, whose handler fetched and ran remote code during a Customizer preview, reaching server code execution. No in-the-wild abuse is reported.

Check
Update all WordPress sites to 7.1.1 immediately, then audit installed themes for unexpected additions and remove any that administrators did not intend.
Affected
Sites where an administrator opens a crafted link can silently install an attacker-chosen theme, which can chain with a vulnerable theme to code execution.
Fix
Apply 7.1.1, remove unused themes, and warn administrators against opening untrusted links while authenticated to the WordPress dashboard.

Malicious repository settings can make AI coding agents run attacker commands

Researchers at Manifold Security disclosed a class of flaws across several command-line AI coding agents in which a repository's own Git configuration names a command that the agent runs automatically on the developer's machine. The command executes outside the agent's sandbox, with the user's privileges, and without any approval prompt, often before the agent even contacts the model. Simply reviewing or opening a malicious project can run attacker code. It triggers when a repository arrives as files with its hidden Git directory intact, such as through a shared drive, archive, or USB stick, rather than a normal clone. Several tools shipped fixes, but some remained vulnerable at disclosure.

Check
Update command-line AI coding agents to patched versions, treat opening or reviewing an untrusted repository in an agentic tool as running its code, and prefer plain clones over copied repositories.
Affected
Developers using command-line AI coding agents who open untrusted repositories delivered as files with their Git directory intact; repository settings can execute attacker commands outside the sandbox, without approval.
Fix
Keep agent tools updated, run them against untrusted code in isolated environments, restrict what the agent can reach, avoid opening repositories from shared drives or archives without inspection, and watch startup commands.

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.

Adobe patches ColdFusion command injection flaw scored a perfect ten

Adobe released Priority 1 updates for ColdFusion and Campaign Classic, led by a critical operating-system command injection flaw in ColdFusion scored 10.0 that could give an attacker arbitrary code execution. Tracked as CVE-2026-48362, it is accompanied by an eval-injection flaw scored 9.9 and an authorization flaw that can cause a denial of service. ColdFusion application servers are a long-standing target for attackers because they are widely internet-exposed and often run with broad access. Adobe is not aware of exploitation yet but urges installation within 72 hours given the priority rating. The Campaign Classic updates apply only to on-premises and hybrid on-premises deployments.

Check
Update ColdFusion to the fixed 2025 and 2023 releases within Adobe's 72-hour window, and confirm internet-facing ColdFusion servers are not running with unnecessary privileges or exposure.
Affected
Organizations running affected Adobe ColdFusion (CVE-2026-48362); an attacker could achieve arbitrary code execution through operating-system command injection, and ColdFusion servers are frequently exposed and targeted.
Fix
Apply the Priority 1 updates quickly, restrict and monitor ColdFusion server access, run it with least privilege, and watch for unexpected process execution, since command-injection flaws are attractive and often weaponized fast.

WordPress pre-auth login XSS can chain to full server takeover

WordPress patched a pre-authentication reflected cross-site scripting flaw in the login screen that researchers showed can chain into PHP code execution and full server takeover, naming the chain XSS2Shell. Tracked as CVE-2026-64638 and scored 8.9, the cross-site scripting bug affects all WordPress versions and needs no login to trigger. On its own it runs script in a visitor's browser, but when a logged-in administrator is lured to an attacker-controlled page, the chain can reach code execution on the server. Because WordPress runs a large share of the web, a flaw affecting every version and needing no authentication has broad reach.

Check
Update WordPress to the patched release across every site, including forgotten and staging installs, and put a web application firewall in front of internet-facing sites.
Affected
All WordPress sites on versions before the fix (CVE-2026-64638); an unauthenticated attacker can run script in the login page, and luring an administrator to a crafted page can chain to code execution.
Fix
Apply the WordPress update, confirm automatic updates ran, use a web application firewall, and remind administrators to avoid unexpected links, since the chain to code execution runs through an admin's browser.

Critical Adobe Campaign Classic flaw gives unauthenticated attackers code execution

Adobe patched a critical flaw in Campaign Classic, its enterprise marketing automation platform, that can let an attacker run code without any user interaction. Tracked as CVE-2026-48449 and scored 10.0, it is an incorrect authorization issue leading to arbitrary code execution in the context of the current user. The same update fixes a high-severity SQL injection flaw that allows arbitrary file reads. Affected versions are Campaign Classic v7 build 9397 and earlier on Windows and Linux, mostly on-premises and hybrid deployments, with a fix in build 9398. Adobe says it is not aware of exploitation, and separately patched eight critical flaws in Adobe Bridge.

Check
Identify on-premises or hybrid Adobe Campaign Classic instances, confirm the build number, and update to 7.4.3 build 9398, prioritizing any instance reachable from untrusted networks.
Affected
Organizations running Adobe Campaign Classic v7 build 9397 or earlier (CVE-2026-48449); the incorrect authorization flaw allows code execution with no user interaction, and a companion flaw enables arbitrary file reads.
Fix
Apply Adobe's update to build 9398, restrict access to the Campaign Classic interface, and review the server for unexpected code execution or file access, since the flaw needs no interaction to exploit.

Security scanners can be turned into a foothold for supply chain attacks

New research shows that application security scanners embedded in the software pipeline can themselves be attacked, because analyzing a repository is not always a read-only action. Many scanners execute code or process files in ways that can be forced to run attacker content when it is handled without isolation. For example, a tool that scans cloud configuration files against a folder of custom rules can be fed a rule that is actually a malicious program, which the scanner runs when it loads it. Since scanners often hold broad access to source, secrets, and build systems, a compromised one is a strong pivot point into the wider environment.

Check
Review how your code and configuration scanners handle untrusted repository content, and check whether they execute rules, plugins, or files without sandboxing and multi-tenant isolation.
Affected
Teams whose security scanners process untrusted repository content without isolation; an attacker controlling a scanned repo can plant content that runs code inside the scanner, which often holds broad access to secrets.
Fix
Run scanners in isolated, least-privilege sandboxes, treat all scanned content as untrusted input, enforce multi-tenancy separation, and limit the source, secrets, and build access that scanning environments hold.

Public exploit runs commands as git on unpatched self-managed GitLab servers

A researcher at depthfirst published a working exploit on July 24 for a GitLab flaw patched on June 10, running commands as the git user on any self-managed 18.11.3 server that has not updated. Any authenticated user who can push to a project can trigger it: the attacker commits a crafted Jupyter notebook and opens its commit diff to leak a heap pointer, repeats until an automated probe locates libraries in memory, then fires the payload with two more notebooks. No administrator rights, runner access, or victim interaction are needed. The bug sits in the notebook renderer, which passes repository-controlled data to a parser inside a long-lived worker.

Check
Move self-managed GitLab to a supported release containing the June fix, and for Helm or Operator deployments verify the GitLab version inside the Webservice image rather than only the chart version.
Affected
Self-managed GitLab servers on 18.11.3 or other unpatched builds; any authenticated user able to push a project can run commands as the git service account, with public exploit code now available.
Fix
Upgrade to a fixed release, since no workaround is offered, and note GitLab did not classify the fix as a security issue, so track upstream library bumps rather than security advisories alone.