A scope bypass vulnerability (CVE-2026-117635) in Gitea allowed a "public-only" access token to access the entire admin API. This flaw enabled such tokens, which should be limited to public resources, to list private organizations and user emails, create new users, promote them to site administrators, and mint Actions runner registration tokens. The issue was due to missing scope checks on the admin API routes. It is fixed in Gitea version 28.3.0. Users are advised to upgrade and audit their admin accounts and Actions runners for unauthorized changes.
CVE-2026-122192 is a vulnerability in Firecracker versions 0.23.0 through 1.16.1 that allows a root user in a guest VM to read or modify memory of the Firecracker process on the host. This occurs when restoring VMs from snapshots using the File memory backend with a balloon or virtio-mem device, due to a failed memory remapping operation that leaves stale host virtual address references. The issue is fixed in Firecracker versions 1.16.2 and 1.17.0 and later. AWS Lambda and other AWS services are not affected. No customer action is required for AWS-managed services.
Two serious vulnerabilities were found in the Rust zip crate, a widely used library for handling ZIP files. The first (RUSTSEC-2026-0367) allows privilege escalation by preserving dangerous file permission bits (setuid, setgid, sticky bit) when extracting archives, potentially enabling attackers to plant setuid-root files. The second (CVE-2026-115905) is a critical remote code execution flaw caused by inconsistent handling of file names between the central directory and local headers in ZIP archives, allowing arbitrary file overwrite and execution. Both vulnerabilities are fixed in version 9.0.5 of the zip crate. The advisory emphasizes that patching alone is insufficient and advocates architectural security using deny-by-default sandboxes to contain untrusted code and limit the impact of such vulnerabilities.
CVE-2026-111497, known as Node2Shell, HTTP2Shell, or Broccoli2Shell, is a remote code execution vulnerability in the Brotli decoder used by official, unmodified Node.js builds. A malformed Brotli compressed request body can trigger an out-of-bounds write, resulting in a shell on the target system. This has been reproduced on x86-64 systems against multiple Node.js targets including plain node:http, official slim images, Express 5.3.0, and Koa 3. The vulnerability arises from improper handling of block switches in Brotli streams, leading to memory corruption and arbitrary code execution. A public scanner is actively mapping Brotli-capable hosts, indicating reconnaissance activity preceding exploitation.
Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JSSE). Supported versions that are affected are Oracle Java SE: 8u511, 8u511-perf, 11.0.33, 17.0.21, 21.0.13, 25.0.5, 27.0.1; Oracle GraalVM for JDK: 17.0.21 and 21.0.13; Oracle GraalVM Enterprise Edition: 21.3.20. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data as well as unauthorized access to critical data or complete access to all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 9.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).
Two critical PHP remote code execution vulnerabilities will be patched in an emergency release on October 21. Fixes are only expected for supported PHP 8.x branches. Key takeaways CVE-2026-109618 and CVE-2026-109619 are critical vulnerabilities in PHP, both rated CVSSv4.0 9.2 by the PHP security team. Public reporting describes both as remote code execution vulnerabilities. watchTowr says it believes it has reproduced CVE-2026-109618, and Cloudflare CTO Dane Knecht says the company is seeing early attacks emerging. The patch release is scheduled for October 21, 2026 at 14:00 UTC. Version numbers reported before the release point to PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. End-of-life branches are not expected to receive fixes. Background Tenable's Research Special Operations (RSO) team has compiled this blog to answer Frequently Asked Questions (FAQ) regarding two critical vulnerabilities in PHP that were announced on October 20, 2026. FAQ When were these PHP vulnerabilities first disclosed? On October 20, 2026, the CVE identifiers circulated on Hacker News and social media. Later that day, the PHP security team published an advance notice of a security release scheduled for October 21 at 14:00 UTC (10:00 AM ET) to address two critical vulnerabilities. The notice said the team could release earlier if details became public or if exploitation appeared in the wild. CERT-EU also published an advisory (2026-018) naming both CVEs. According to watchTowr , the vulnerabilities were originally set to be disclosed on Thursday, October 22, under embargo. A video shared by researcher Kirill Firsov demonstrates the exploit chain, dubbed php2shell. Firsov credited the video and exploit to researcher LCFR and Calif.io. The PHP security team is giving advance notice: Upcoming security release Wed, Oct 21st 2026, 14:00UTC, two critical vulnerabilities, both rated CVSSv4 9.2. PHP users are encouraged to prepare to update. Earlier release if details become public or active exploit evidence. — The PHP Foundation (@ThePHPF) October 20, 2026 What are CVE-2026-109618 and CVE-2026-109619? CVE Description CVSSv4.0 CVE-2026-109618 Unspecified PHP Vulnerability 9.2 CVE-2026-109619 Unspecified PHP Vulnerability 9.2 CVE-2026-109618 and CVE-2026-109619 are critical vulnerabilities in PHP. Public reporting describes both as remote code execution vulnerabilities. The PHP security team has not published technical details before the patch release. CVSS scores differ across sources. The PHP security team rates both vulnerabilities as CVSSv4.0 9.2. Some early reports, including watchTowr and a Hacker News post, describe them as CVSS 10.0. We will update this blog once PHP publishes its advisory. Which PHP versions are affected? CERT-EU says these vulnerabilities could affect all PHP versions from PHP 5 onwards, and the demonstration video references PHP 5.4.0 and later. PHP will publish the official list of affected and fixed versions with the release. Before the release, security researcher Kevin Beaumont reported the following fixed versions: Affected Versions Fixed Version (expected) PHP 8.5.x 8.5.12 PHP 8.4.x 8.4.27 PHP 8.3.x 8.3.36 PHP 8.2.x 8.2.35 PHP 5.x through 8.1.x End-of-life, no fix expected Linux distributions that ship older PHP packages may backport fixes, so organizations using distribution packages should check their vendor's advisories. How widespread is PHP, and how many hosts are potentially affected? According to W3Techs , PHP is used by 69.3% of websites whose server-side language is known. Platforms such as WordPress, Drupal, Joomla, Laravel and Magento all run on PHP. Security researcher Silas Cutler's rough estimate is that over 1.3 million internet-exposed hosts are potentially vulnerable. A Shodan search by Henk Poley counts over 1.9 million internet-exposed hosts running PHP. Has exploitation been observed in the wild? On October 21, Cloudflare CTO Dane Knecht said the company is "seeing early attacks emerging" and is updating its miti…
CVE-2026-79417 is a local denial-of-service vulnerability in Argus Monitor caused by an exposed IOCTL that allows unprivileged users to disable the x86 MONITOR and MWAIT instructions. Exploiting this vulnerability requires leveraging a time-of-check to time-of-use (TOCTOU) bug related to the SeLocateProcessImageName function. Successful exploitation triggers a HYPERVISOR_ERROR bugcheck, impacting Hyper-V and other kernel components that rely on these instructions.
CVE-2026-86776 is a reported medium severity vulnerability affecting KeePass. The available information is limited, with no technical details, affected versions, or patch status provided. There is no evidence of exploitation in the wild. The vulnerability was referenced in a Reddit cybersecurity post linking to an external vulnerability database, but no further specifics are available.
CVE-2026-17106, known as CopyEscape, is a high-severity vulnerability in Docker's 'docker cp' command that allows a malicious container to write arbitrary files to the host filesystem. The flaw stems from a filesystem race condition during archive creation combined with unsafe symbolic link handling during extraction. This can lead to arbitrary file creation or overwriting on the host and potentially code execution depending on the privileges of the Docker CLI user. Docker has released official fixes in Docker Engine/CLI version 29.7.2 and later, Docker Desktop 4.86.0 and later, and Docker Sandboxes 0.38.0 and later.
CVE-2026-64638 is a high-severity pre-authentication reflected cross-site scripting (XSS) vulnerability in WordPress login pages that can lead to remote code execution (RCE) under specific conditions. The flaw allows attacker-controlled JavaScript to execute in the browser of a visitor after a failed login attempt. Exploitation requires a logged-in administrator to interact with an attacker-controlled page, potentially enabling PHP code execution on the server. The vulnerability affects default WordPress installations and was patched in WordPress 7.0.3 and backported to versions back through 4.7. Versions older than 4.7 remain vulnerable. WordPress recommends immediate updating, and automatic background updates should apply the patch automatically. No in-the-wild exploitation has been reported as of the advisory date.
CVE-2026-17583 is a vulnerability in Thermo Fisher's Applied Biosystems human identification instruments where forensic DNA evidence files (.fsa and .hid) can be altered between creation and analysis without detection. Researchers demonstrated that these files could be modified in about 45 minutes to merge DNA profiles into a single file that appears unaltered since 2015. Thermo Fisher issued an update adding digital signatures to files created after the patch, but no retroactive validation exists for older files, and some end-of-life products do not receive updates. This leaves historical forensic DNA evidence files vulnerable to undetectable tampering.
CVE-2026-0286 is an authenticated command injection vulnerability in the PAN-OS CLI that allows an attacker with administrative CLI access to execute arbitrary commands on the underlying system by escaping the CLI environment. The vulnerability affects PAN-OS versions prior to 12.1.8, 11.2.13, 11.1.16, and 10.2.18-h8. Cloud NGFW services are not affected. Palo Alto Networks has released patches for these versions. A temporary mitigation is available via Threat Prevention subscription with Threat ID 510036, but it requires inbound management traffic decryption and is not a full fix. Patching is the recommended remediation.
CVE-2026-25262 is a write-what-where vulnerability in the Qualcomm Sahara protocol experimentally confirmed on the Snapdragon 8 Gen 1 (SM8450) platform. It allows arbitrary writes to SRAM during the Sahara handshake, bypassing signature verification and partially bypassing Firehose loader authorization. The loader executes and responds to commands without authorization errors, but full UFS storage access has not yet been achieved. The vulnerability was previously known only on legacy 32-bit Qualcomm platforms but now affects modern 64-bit ARMv9 SoCs. No official patch or remediation guidance is currently available, and research is ongoing to achieve full Firehose initialization and understand TrustZone dependencies.
CVE-2026-23111 is a use-after-free vulnerability in the Linux kernel's nftables subsystem, introduced by a flawed security fix for a previous vulnerability (CVE-2023-4244). It affects Container-Optimized OS nodes and can lead to privilege escalation. Google Kubernetes Engine (GKE) Standard clusters are impacted, while Autopilot clusters are not vulnerable by default unless specific insecure configurations are used. Patch versions have been released for Ubuntu node pools and Container-Optimized OS node pools on GKE. Other GKE environments (AWS, Azure) and VMware are pending patch and severity updates. Bare metal GDC software is not affected as it does not include an OS. The vulnerability is rated high severity. Detection techniques focus on monitoring behavior rather than payload signatures, applicable even on patched kernels.
CVE-2026-39949 is an authenticated remote code execution vulnerability in Cacti versions up to and including 1.2.30. The flaw arises from unsanitized variable substitution in RRDtool command-line arguments, allowing users with graph management privileges to inject arbitrary OS commands via host metadata fields such as the device notes. Exploitation requires authenticated access with permissions to create devices and graph templates. An attacker can craft malicious input in the notes field and trigger code execution during graph rendering.
CVE-2026-45447 is a use-after-free vulnerability in OpenSSL's PKCS#7 signature verification that occurs when processing specially crafted PKCS#7 or S/MIME signed messages containing an empty ASN.1 SET in the SignedData digestAlgorithms field. This flaw causes OpenSSL to incorrectly free a caller-owned BIO during PKCS7_verify(), potentially leading to crashes, heap corruption, or remote code execution. Applications using OpenSSL PKCS#7 APIs are affected, while those using CMS APIs or FIPS modules are not impacted. The vulnerability has been addressed by OpenSSL in official commits.
An autonomous AI agent developed by the security startup depthfirst discovered 21 zero-day vulnerabilities in the FFmpeg multimedia framework, including nine assigned CVEs (CVE-2026-39210 through CVE-2026-39218). These vulnerabilities primarily involve heap and stack overflows in various parsers and demuxers, with some bugs dating back to 2003. FFmpeg maintainers have been responsive and are shipping fixes. The discovery raises concerns about the effectiveness of traditional static and dynamic analysis tools against memory corruption in large C codebases and the potential impact of AI-driven vulnerability discovery on disclosure pipelines and vulnerability economics.
On May 27, 2026, multiple critical supply chain vulnerabilities were disclosed affecting popular packages across npm, PyPI, Composer, Cargo, Maven, and GitHub Actions ecosystems. The FUXA package is vulnerable to unauthenticated remote code execution via path manipulation and script test mode authorization bypass. Several widely used packages including Laravel Lang, durabletask, AntV, node-ipc, TanStack, and lightning have been compromised through malicious republishing or maintainer account compromises, risking credential theft and arbitrary code execution. Additional high-severity issues include authorization bypasses and deserialization vulnerabilities in other packages. Immediate remediation involves upgrading affected packages or auditing and uninstalling compromised ones as recommended. These vulnerabilities underscore ongoing risks in software supply chains and the critical importance of dependency management.
CVE-2025-40602 is a high-severity vulnerability affecting SonicWall SMA 100 series appliances, which are critical for secure remote access and network security. The vulnerability has been actively exploited in the wild, allowing attackers to potentially gain unauthorized access or disrupt services without requiring user interaction. European organizations relying on these appliances, especially in sectors dependent on VPN and remote access, face significant risk. Immediate patching, enhanced monitoring, and network segmentation are essential mitigation steps. Germany, France, and the UK are the most likely affected countries due to high SonicWall market penetration and critical infrastructure reliance. The threat impacts confidentiality and availability, with ease of exploitation and broad scope, warranting a high severity rating. Defenders should prioritize applying patches, reviewing access logs, and reinforcing perimeter defenses to mitigate this threat effectively.