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 (CISA) added four vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog on November 18, 2026, after confirming real-world exploitation. The affected products are Apache Axis, REDCap, Synology DSM, and LiteLLM. Federal agencies must now remediate these issues within prescribed deadlines.
CVE-2026-90436 impacts the Apache Axis web services framework used for SOAP-based communication between applications. Attackers can send a specially crafted SOAP fault message to load arbitrary classes without authentication, leading to remote code execution under certain conditions.
CVE-2026-90817 affects Research Electronic Data Capture (REDCap), a widely used platform for collecting and managing research data. The flaw resides in the public survey processing and data import modules. An attacker who obtains a valid survey hash can deliver a malicious HTTP request that executes arbitrary code on the server without authentication.
The two additional vulnerabilities in Synology DSM and LiteLLM were also confirmed as actively exploited, although technical details remain limited in the current advisory. CISA emphasizes that all four flaws carry a high risk of widespread abuse.
Security teams should review the official KEV catalog and prioritize patching or mitigation steps for any exposed instances of the listed products.
Related articles
PHP Prepares Critical Patches for All Supported Versions One Month After Emergency Update
The PHP development team announced on November 18 that it will release updates for all supported interpreter versions to address multiple vulnerabilities, including critical ones. The fixes target a use-after-free flaw in file upload progress tracking that can lead to remote code execution when specific session serialization formats are combined. This comes shortly after emergency patches issued on October 21 resolved two remote code execution issues collectively known as PHP2Shell. The new vulnerability, tracked as CVE-2026-115560 with a CVSS score of 9.8, arises when applications switch session formats from php_binary or php_serialize to php after upload tracking has begun. Developers are advised to disable session.upload_progress.enabled until patches are applied and verified. Releases are scheduled for November 19 between 17:00 and 17:30 Moscow time, accompanied by a detailed security bulletin.
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.
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.
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.