Habr•November 19, 2026•🇷🇺Translated from Russian

PHP Prepares Critical Patches for All Supported Versions One Month After Emergency Update

The PHP development team announced on November 18 that it will issue updates for all supported versions of the interpreter to address several vulnerabilities, including critical flaws that require non-standard configurations or specific environments for exploitation.

The upcoming releases, scheduled for November 19 between 17:00 and 17:30 Moscow time, follow emergency patches released on October 21 that resolved two remote code execution vulnerabilities known as PHP2Shell. Two days later, developers disclosed another code execution path involving file upload progress tracking, assigned the identifier CVE-2026-115560.

Security firm Aikido expects the fix to arrive with the November 19 release, as the PHP team promised a full bulletin alongside the regular update cycle. In the CodeScoring knowledge base, the vulnerability carries a critical severity rating of 9.8 under CVSS 3.0 and stems from a use-after-free condition triggered during processing of specially crafted POST requests.

File upload progress tracking stores session data on the server before the application starts. The flaw occurs when the session serialization format is set to php_binary or php_serialize for tracking, after which the application switches the format to php. Under these conditions, an attacker can craft a request that results in arbitrary code execution on the server.

Until patches are available, PHP recommends disabling upload progress tracking by setting session.upload_progress.enabled=0 in the server configuration and restarting all PHP worker processes. Applications that never change session formats during runtime do not need to disable the feature for protection.

Related articles

Security NEXT•Vulnerabilities & Exploits

WordPress 7.1.5 Released to Patch Multiple Vulnerabilities Including Privilege Escalation

The WordPress development team has issued version 7.1.5 to resolve more than 20 security issues spanning privilege escalation, remote code execution risks, SQL injection, and cross-site scripting flaws. The update specifically addresses an attribute-based vulnerability in the Template Part block that could allow attackers to escalate privileges and potentially execute arbitrary code. A separate flaw in multisite environments enables site administrators to hijack super-admin accounts by abusing the customizer menu preview feature. Two SQL injection vulnerabilities and multiple XSS issues were also corrected, along with information disclosure problems. Sites configured for automatic background updates will receive the patch automatically, while manual updates remain available through the admin dashboard. Backports are being rolled out for branches starting from WordPress 4.7.

Security NEXT•Vulnerabilities & Exploits

CISA Adds Four Actively Exploited Vulnerabilities to KEV Catalog Targeting Apache Axis, REDCap, Synology DSM and LiteLLM

The U.S. Cybersecurity and Infrastructure Security Agency has added four vulnerabilities to its Known Exploited Vulnerabilities catalog after confirming active exploitation in the wild. The flaws affect Apache Axis, REDCap, Synology DSM, and LiteLLM, prompting mandatory remediation for federal agencies. CVE-2026-90436 in Apache Axis allows unauthenticated remote code execution via crafted SOAP fault messages under specific conditions. CVE-2026-90817 in REDCap enables unauthenticated remote code execution through manipulated HTTP requests targeting public survey and data import functions, provided an attacker knows a valid survey hash. The remaining two vulnerabilities in Synology DSM and LiteLLM were also confirmed exploited but lack detailed public descriptions at this time. Organizations are urged to apply patches immediately to prevent further attacks.

AntiMalware•Vulnerabilities & Exploits

NGINX Patches Critical Remote Code Execution Vulnerability Present Since 2015 (CVE-2026-123007)

NGINX has released patches for a critical vulnerability, CVE-2026-123007, that allowed unauthenticated remote code execution on servers with HTTP/2 enabled. The flaw existed in the codebase since version 1.9.5 released in 2015 and was fixed in versions 1.30.7 and 1.31.9 on November 18. Researchers at Wiz discovered that improper handling of HTTP/2 flow control counters leads to memory corruption, enabling code execution that bypasses ASLR and runs with the privileges of the NGINX worker process. The vulnerability affects even servers serving only static files without backend application connections. A second related issue, CVE-2026-123633, involving use-after-free in HTTP/2 handling, was also addressed in the same updates. Administrators are advised to apply the patches immediately or disable HTTP/2 as a temporary mitigation if updates cannot be installed promptly. No in-the-wild exploitation of CVE-2026-123007 had been observed at the time of disclosure.

Securitylab•Vulnerabilities & Exploits

Managing Bug Bounty Programs: Handling Report Overload, Duplicates, and AI-Generated Submissions

Launching a bug bounty program is only the beginning; the real challenge lies in managing the influx of reports, filtering duplicates and AI-generated noise, and ensuring vulnerabilities are actually fixed. Standoff Bug Bounty recommends starting with private programs limited to 30-50 researchers to build internal processes before scaling. Companies like Flavau developed custom DevSecOps consoles that cut report triage time by a factor of 10 by automating duplicate detection and assignee assignment. The platform introduced neural slop windows that limit submissions based on researcher quality history, addressing the surge in AI-generated invalid reports observed in spring 2026. Fixed response timelines, clear ownership roles, and prioritized remediation of critical issues help maintain program effectiveness. Google’s decision to pause its OSS VRP in October 2026 due to automated report floods highlights broader industry concerns, yet experts maintain that human-driven independent validation remains essential. Key success metrics include reduced risk from fixed high-severity issues, lower average payout costs, and improved cross-team communication between security and development.