# Tenable

The leader in exposure management and AI security, Tenable cybersecurity solutions reduce cyber risk across IT, OT, cloud, identity & hybrid attack surfaces.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## How exposure management can help public sector prepare for PHP2Shell-like vulnerabilities

DevFeed: [How exposure management can help public sector prepare for PHP2Shell-like vulnerabilities](<https://devfeed.tech/articles/how-exposure-management-can-help-public-sector-prepare-for-php2shell-like-vulnerabilities-146992.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/public-sector-exposure-management-php2shell>)

Author: Kate Boronkay

Published: 2026-11-20T14:00:00Z

Content type: article

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [Exposure Management](<https://devfeed.tech/topics/exposure-management.md>), [Endpoint security](<https://devfeed.tech/topics/endpoint-security.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>), [Security research](<https://devfeed.tech/topics/security-research.md>), [cybersecurity and infrastructure security agency](<https://devfeed.tech/topics/cybersecurity-and-infrastructure-security-agency.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>)

Tags: [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [php](<https://devfeed.tech/tags/php.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [public-sector](<https://devfeed.tech/tags/public-sector.md>)

### AI overview

PHP2Shell was confirmed exploited within days of disclosure, and many teams first struggled to find every affected runtime across infrastructure, cloud workloads, and third-party products. The article recommends continuous asset and vulnerability visibility, prioritizing by KEV status, exploit predictions, and internet exposure alongside severity, and preparing compensating controls for systems that cannot be patched promptly. It also urges teams to map what an attacker could reach from an edge foothold, then patch kernels, restrict unprivileged user namespaces, and limit appliance access to management networks and directory services. For federal civilian agencies, BOD 26-04 uses public exposure, KEV status, exploit automation potential, and technical impact to tier remediation; state, local, and education teams are encouraged to use similar prioritization. Tenable describes products for discovering PHP assets, detecting vulnerable versions, scanning applications and cloud workloads, and managing remediation; the article also names Tenable Security Center for on-premises and air-gapped settings.

### Source excerpt

PHP2Shell showed how fast a runtime-level flaw can go from disclosure to confirmed exploitation. Here's how federal, state, local, and education teams can prepare for PHP2Shell-like flaws. Key takeaways PHP2Shell went from disclosure to confirmed exploitation within days. With AI shortening the disclosure-to-exploitation window, new critical flaws will likely move just as fast. Most security teams' primary challenge with PHP2Shell was knowing where the vulnerabilities were in their environment. Teams that already knew where PHP ran across their IT infrastructure, web applications, and cloud assets were in a position to act quickly. Initial access flaws will continue to impact your network edge, so work backward from the foothold. Map what an attacker could reach after breaching an edge device, such as root access, management servers, and directory services. Then close those escalation paths by patching kernels and restricting unprivileged user namespaces. To prioritize, factor in exploitation evidence, not severity alone. Weigh KEV status, exploit prediction scores, and your own internet exposure, as well as pre-approve a plan for systems you can't patch immediately. When two critical PHP vulnerabilities, nicknamed PHP2Shell, leaked ahead of their coordinated disclosure date on Oct. 20, and their alarming scope and severity became clear, cybersecurity teams sprung into "all hands on deck" mode, much in the same way they did in late 2021 in response to the Log4Shell bug. Many organizations, including government agencies, rushed to take down their websites as an early, stopgap preventive measure against attackers' already active attempts to exploit these two memory management vulnerabilities, which were cataloged as CVE-2026-109618 and CVE-2026-109619 and given a CVSS score of 9.2. Thrust into a furious race against time, security teams scrambled to detect and patch their instances of PHP, the popular server-side scripting language that around 70% of websites use. If

## NGINX2Root (CVE-2026-123007): Frequently asked questions about five critical NGINX vulnerabilities

DevFeed: [NGINX2Root (CVE-2026-123007): Frequently asked questions about five critical NGINX vulnerabilities](<https://devfeed.tech/articles/nginx2root-cve-2026-123007-frequently-asked-questions-about-five-critical-nginx-vulnerabilities-141980.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/nginx2root-cve-2026-123007-frequently-asked-questions-about-five-critical-nginx>)

Author: Alexis Clark

Published: 2026-11-19T00:18:05Z

Content type: article

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [nginx](<https://devfeed.tech/topics/nginx.md>), [Security research](<https://devfeed.tech/topics/security-research.md>), [Linux Kernel](<https://devfeed.tech/topics/linux-kernel.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [aslr](<https://devfeed.tech/tags/aslr.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-123007](<https://devfeed.tech/tags/cve-2026-123007.md>), [f5](<https://devfeed.tech/tags/f5.md>), [faq](<https://devfeed.tech/tags/faq.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [github](<https://devfeed.tech/tags/github.md>), [http-2](<https://devfeed.tech/tags/http-2.md>), [http-3](<https://devfeed.tech/tags/http-3.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-kernel](<https://devfeed.tech/tags/linux-kernel.md>), [local-privilege-escalation](<https://devfeed.tech/tags/local-privilege-escalation.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [nginx2root](<https://devfeed.tech/tags/nginx2root.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

NGINX2Root refers to five critical NGINX memory-corruption flaws plus a separate, unpatched Linux kernel SCTP use-after-free that Xint says can chain from NGINX worker access to root. CVE-2026-123007 is the most urgent: unauthenticated code execution is possible when HTTP/2 over TLS is enabled. A public PoC exists, but Rapid7 describes it as constrained: it targets x86-64 builds, needs about 128 GB of HTTP/2 traffic, must defeat ASLR, and may fail behind HTTP/2-terminating proxies or on slow connections. F5's November 18, 2026 out-of-band release fixed these five flaws and five others. The source says there were no reports of exploitation in the wild as of that date. Patching is the fix; restart NGINX after upgrading, since a configuration reload does not replace the running executable. Mitigations cover only some flaws: disabling HTTP/2 leaves three of the five NGINX issues unaddressed. For hosts not using SCTP, Xint recommends blocking the kernel SCTP module until a kernel fix is available.

### Source excerpt

Frequently asked questions about five critical NGINX remote code execution vulnerabilities and five additional flaws fixed in F5's November 18 out-of-band release. Key takeaways NGINX2Root is associated with five critical remote code execution vulnerabilities in NGINX, and a separate, unpatched Linux kernel local privilege escalation (LPE) flaw that can be chained with the NGINX bugs to gain root. CVE-2026-123007 is the most urgent of the five. It is an unauthenticated RCE flaw in NGINX's HTTP/2 implementation and requires only HTTP/2 over TLS to be enabled. A PoC is publicly available on GitHub. F5's November 18 release fixed the five NGINX2Root vulnerabilities and five additional NGINX flaws. Background Tenable's Research Special Operations (RSO) team has compiled this blog to answer Frequently Asked Questions (FAQ) regarding NGINX2Root, a set of five critical remote code execution vulnerabilities in NGINX, and five additional NGINX flaws that F5 fixed in an out-of-band security release on November 18, 2026. FAQ What is NGINX2Root? NGINX2Root is the name Xint (Theori) gave to five critical remote code execution vulnerabilities in NGINX, and a separate, unpatched Linux kernel local privilege escalation (LPE) flaw that Xint says can be chained with the NGINX bugs to gain root. The NGINX flaws are memory-corruption bugs in HTTP/2, HTTP/3, the resolver, and the mail proxy module. Exploitation depends on the specific feature being active, and achieving code execution generally requires ASLR to be absent or defeated. The name is not used by F5 or nginx.org. What are the vulnerabilities associated with NGINX2Root? CVEDescriptionCVSSv4 (F5)CVE-2026-123007NGINX ngx_http_v2_module vulnerability9.2CVE-2026-123633NGINX ngx_http_v2_module vulnerability9.2CVE-2026-123634NGINX resolver vulnerability9.2CVE-2026-121810NGINX ngx_http_v3_module vulnerability9.2CVE-2026-113425NGINX ngx_mail_proxy_module vulnerability9.2 Xint also identified a separate, unpatched Linux kernel SCTP use

## Fix Tenable One findings where developers work: Tenable and OpenAI Daybreak Defense Factory

DevFeed: [Fix Tenable One findings where developers work: Tenable and OpenAI Daybreak Defense Factory](<https://devfeed.tech/articles/fix-tenable-one-findings-where-developers-work-tenable-and-openai-daybreak-defense-factory-140732.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/openai-connector-tenable-one-codex-security>)

Author: Team Tenable

Published: 2026-11-18T13:00:00Z

Content type: release

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [codex](<https://devfeed.tech/topics/codex.md>), [OpenAI](<https://devfeed.tech/topics/openai.md>), [developer-productivity](<https://devfeed.tech/topics/developer-productivity.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [cli](<https://devfeed.tech/tags/cli.md>), [code](<https://devfeed.tech/tags/code.md>), [code-security](<https://devfeed.tech/tags/code-security.md>), [codex](<https://devfeed.tech/tags/codex.md>), [context](<https://devfeed.tech/tags/context.md>), [csv](<https://devfeed.tech/tags/csv.md>), [customers](<https://devfeed.tech/tags/customers.md>), [daybreak](<https://devfeed.tech/tags/daybreak.md>), [defense](<https://devfeed.tech/tags/defense.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developers](<https://devfeed.tech/tags/developers.md>), [development](<https://devfeed.tech/tags/development.md>), [export](<https://devfeed.tech/tags/export.md>), [factory](<https://devfeed.tech/tags/factory.md>), [one](<https://devfeed.tech/tags/one.md>), [openai](<https://devfeed.tech/tags/openai.md>), [tenable](<https://devfeed.tech/tags/tenable.md>), [tenable-one](<https://devfeed.tech/tags/tenable-one.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

OpenAI's Codex Security connector brings selected Tenable One code findings into a developer's local workbench with the finding name, severity, state, Tenable description and solution, and the Tenable finding ID. It reads selections through Tenable One's Inventory Export API or from CSV exports; file paths and line numbers are retained when provided. To import, select a repository and findings, export them, preview against the local checkout with `codex-security publish findings --provider tenable --dry-run`, then rerun and confirm to save. Imported findings start as "not assessed." Reimporting with the same source key, tenant alias and asset ID updates changed evidence while leaving identical findings as they are. The text presents the integration as a way to reduce developers' need to reconstruct context lost when findings arrive through tickets or exports.

### Source excerpt

Tenable One customers can now bring selected findings into OpenAI Daybreak Defense Factory through a local Codex Security CLI import with Tenable's description and solution attached, so developers can fix them where they already work. OpenAI built the connector, one of the select supported integrations in the OpenAI Daybreak Defense Factory. Key takeaways Code security findings often lose their context in the handoff. Security teams pass code findings to developers as exports and tickets, and developers end up reinvestigating before they can fix anything. Daybreak Defense Factory imports selected Tenable One findings. OpenAI built a Tenable One connector into Codex Security, which OpenAI publishes as open source. The connector reads findings through the Inventory Export API in Tenable One or from CSV exports. Each finding arrives in the local Codex Security workbench with its name, severity and state, plus Tenable's description and solution. You can try it today with OpenAI's setup guide. Select a code repository and its findings in Tenable One, export them, then preview and import them into Codex Security against your local checkout of the repository. Why code findings stall between security and development A vulnerability often takes an indirect path from the security team that finds it to the developer who fixes it, and important context gets lost along the way. The security team sends the finding over as an export or a ticket, where a development team triages it. When a developer finally picks it up, they still have to work out which code is affected and what a good fix looks like before they can write a line of code to fix it. Most of that context already existed on the security side. It just didn't make the trip. We think the fix should start where the developer already works. That's the idea behind Tenable One's integration with OpenAI Daybreak Defense Factory: the security team selects findings in Tenable One, and the developer imports them locally with the

## Java4Shell (CVE-2026-114938): Frequently asked questions about OpenJDK remote code execution vulnerability

DevFeed: [Java4Shell (CVE-2026-114938): Frequently asked questions about OpenJDK remote code execution vulnerability](<https://devfeed.tech/articles/java4shell-cve-2026-114938-frequently-asked-questions-about-openjdk-remote-code-execution-vulnerability-139430.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/java4shell-cve-2026-114938-frequently-asked-questions-about-openjdk-rce-vulnerability>)

Author: Satnam Narang

Published: 2026-11-18T02:49:16Z

Content type: article

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [openjdk](<https://devfeed.tech/topics/openjdk.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [applications](<https://devfeed.tech/tags/applications.md>), [atlassian-jira](<https://devfeed.tech/tags/atlassian-jira.md>), [avx-512-vbmi](<https://devfeed.tech/tags/avx-512-vbmi.md>), [base64](<https://devfeed.tech/tags/base64.md>), [bug](<https://devfeed.tech/tags/bug.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [execution](<https://devfeed.tech/tags/execution.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [java4shell](<https://devfeed.tech/tags/java4shell.md>), [openjdk](<https://devfeed.tech/tags/openjdk.md>), [questions](<https://devfeed.tech/tags/questions.md>), [remote](<https://devfeed.tech/tags/remote.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [remote-code-execution-vulnerability](<https://devfeed.tech/tags/remote-code-execution-vulnerability.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

Java4Shell (CVE-2026-114938) is an OpenJDK memory corruption flaw in an optimized Base64 decoder. A specially crafted string can write beyond its allocated memory, potentially exposing application memory or enabling remote code execution without login when an application passes untrusted data to the affected APIs. Exposure requires an affected Java version and an x86-64 processor supporting AVX-512 VBMI; Calif says ARM64 is not affected. OpenJDK lists Java 17, 21, 25 and 27 release lines, and OpenJDK-based distributions may also be vulnerable. Oracle issued fixes on November 17, 2026; other vendors release fixes on their own schedules. Calif's PoC triggers the bug but does not establish that a particular application is exposed. Calif says exploits must be adapted per application, and failed attempts may crash it. Calif identified startup options -XX:-UseBASE64Intrinsics and -XX:UseAVX=2 to disable the vulnerable code path, with the latter limited to x86-64 and incompatible with Java startup on ARM. As of November 17, Tenable knew of no in-the-wild exploitation reports.

### Source excerpt

Java4Shell is a flaw in how Java decodes Base64 data. Calif, which found it, says it can let attackers run code on widely used Java applications without logging in. Oracle released fixed Java builds on November 17, and Calif is withholding its exploits for individual applications for now. Key takeaways CVE-2026-114938, dubbed Java4Shell, is an OpenJDK memory corruption vulnerability that Oracle scores 8.1 on CVSS 3.1, and Calif says its testing showed attackers could run code without logging in on applications such as Atlassian Jira and Jenkins. As of November 17, Tenable is not aware of any reports that attackers have exploited this flaw, though Calif has published a PoC that triggers the bug without taking control of the system and a second researcher reports building a working exploit. Oracle released fixed builds on November 17, and according to Calif, only systems running an affected Java version on x86-64 processors that support AVX-512 VBMI can be affected. Background Tenable's Research Special Operations (RSO) team has compiled this blog to answer Frequently Asked Questions (FAQ) regarding Java4Shell, a vulnerability in OpenJDK that was patched on November 17, 2026. FAQ When was Java4Shell first disclosed? On November 17, security firm Calif said on X that it had found and reported the flaw, and that details of Java4Shell, as Calif named it, had leaked ahead of a fix. Later that day, Oracle released its November 2026 Critical Security Patch Update (CSPU), and the OpenJDK Vulnerability Group published its own advisory. Calif then published its technical write-up. Oracle credits Quang Luong of Calif.io and Albert Yang for reporting the vulnerability. Since the vulnerability has leaked: Calif discovered and reported Java4Shell (CVE-2026-114938). We're publishing technical details by 1 PM Pacific today, after Oracle releases a patch. Stay tuned! https://t.co/No5hJXK1Zx -- Calif (@calif_io) November 17, 2026 What is CVE-2026-114938? CVEDescriptionCVSSv3.1CVE-2026-

## Oracle November 2026 Critical Security Patch Update Addresses 640 CVEs (CVE-2026-114938)

DevFeed: [Oracle November 2026 Critical Security Patch Update Addresses 640 CVEs (CVE-2026-114938)](<https://devfeed.tech/articles/oracle-november-2026-critical-security-patch-update-addresses-640-cves-cve-2026-114938-139431.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/oracle-november-2026-critical-security-patch-update-addresses-640-cves-cve-2026-114938>)

Author: Research Special Operations

Published: 2026-11-17T21:45:17Z

Content type: news

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [patches](<https://devfeed.tech/topics/patches.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>)

Tags: [17](<https://devfeed.tech/tags/17.md>), [2026](<https://devfeed.tech/tags/2026.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [cves](<https://devfeed.tech/tags/cves.md>), [graalvm](<https://devfeed.tech/tags/graalvm.md>), [hyperion](<https://devfeed.tech/tags/hyperion.md>), [java](<https://devfeed.tech/tags/java.md>), [java-se](<https://devfeed.tech/tags/java-se.md>), [java4shell](<https://devfeed.tech/tags/java4shell.md>), [medium](<https://devfeed.tech/tags/medium.md>), [monthly](<https://devfeed.tech/tags/monthly.md>), [november-2026](<https://devfeed.tech/tags/november-2026.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [patch](<https://devfeed.tech/tags/patch.md>), [security](<https://devfeed.tech/tags/security.md>), [security-patch](<https://devfeed.tech/tags/security-patch.md>), [update](<https://devfeed.tech/tags/update.md>)

### AI overview

Oracle's November 2026 Critical Security Patch Update fixes 640 CVEs through 655 security updates across 21 product families. It includes 62 critical updates covering 57 CVEs; medium and high severity account for 41.8% and 38% of patches, respectively. Hyperion received 267 patches (40.8%), the most of any family, followed by Supply Chain with 74 (11.3%). The update also patches CVE-2026-114938, dubbed "Java4Shell," in the Compiler component of Oracle Java SE and GraalVM; its CVSSv3 score is 8.1. Technical details were expected later. Customers are advised to apply all relevant patches and consult Oracle's November advisory for details.

### Source excerpt

Oracle addresses 640 CVEs in its November 2026 Critical Security Patch Update with 655 patches, including 62 critical updates. Key Takeaways The November 2026 Critical Security Patch Update (CSPU) contains fixes for 640 unique CVEs in 655 security updates 62 issues (9.5% of all patches) were assigned a critical severity rating Oracle Hyperion received the highest number of patches at 267, accounting for 40.8% of all patches Background On November 17, Oracle released its Critical Security Patch Update (CSPU) for November 2026. Beginning in May 2026, Oracle introduced CSPUs as a monthly release cycle that sits between the larger quarterly Critical Patch Updates (CPUs), addressing a focused set of high-severity issues on a faster cadence. This CSPU contains fixes for 640 unique CVEs in 655 security updates across 21 Oracle product families. Out of the 655 security updates published, 9.5% of patches were assigned a critical severity. Medium severity patches accounted for the bulk of security patches at 41.8%, followed by high severity patches at 38%. This month's update includes 62 critical patches across 57 CVEs. SeverityIssues PatchedCVEsCritical6257High249245Medium274268Low7070Total655640 Analysis This month's update saw the Oracle Hyperion product family contain the highest number of patches at 267, accounting for 40.8% of the total patches, followed by Oracle Supply Chain at 74 patches, which accounted for 11.3% of the total patches. Oracle CSPU includes patches for Java4Shell (CVE-2026-114938) As part of the November CSPU release, Oracle patched CVE-2026-114938, a vulnerability in the Compiler component of Oracle Java SE and GraalVM. It was assigned a CVSSv3 score of 8.1. Researchers have dubbed this flaw "Java4Shell" and technical details about this vulnerability are expected to be released soon. The Research Special Operations (RSO) team plans to publish a FAQ blog post on the Tenable blog with more detail. A full breakdown of the patches for this CSPU can be se

## Able2Shell: Frequently asked questions for reported N-able N-central zero-day vulnerabilities

DevFeed: [Able2Shell: Frequently asked questions for reported N-able N-central zero-day vulnerabilities](<https://devfeed.tech/articles/able2shell-frequently-asked-questions-for-reported-n-able-n-central-zero-day-vulnerabilities-128940.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/able2shell-frequently-asked-questions-for-reported-n-able-n-central-zero-day-vulnerabilities>)

Author: Research Special Operations

Published: 2026-11-11T05:55:43Z

Content type: news

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>)

Tags: [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-91000](<https://devfeed.tech/tags/cve-2026-91000.md>), [cves](<https://devfeed.tech/tags/cves.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [faq](<https://devfeed.tech/tags/faq.md>), [github](<https://devfeed.tech/tags/github.md>), [honeypots](<https://devfeed.tech/tags/honeypots.md>), [hotfix](<https://devfeed.tech/tags/hotfix.md>), [n-able](<https://devfeed.tech/tags/n-able.md>), [n-central](<https://devfeed.tech/tags/n-central.md>), [proof-of-concept](<https://devfeed.tech/tags/proof-of-concept.md>), [security-researcher](<https://devfeed.tech/tags/security-researcher.md>), [security-updates](<https://devfeed.tech/tags/security-updates.md>), [tenable](<https://devfeed.tech/tags/tenable.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [zero-day](<https://devfeed.tech/tags/zero-day.md>), [zero-day-vulnerabilities](<https://devfeed.tech/tags/zero-day-vulnerabilities.md>)

### AI overview

Able2Shell is a researcher's set of 33 alleged N-central vulnerabilities with proof-of-concept code; N-able has published seven CVEs and released N-central 2026.4 Hotfix 2 (build 2026.4.1.26) to address them, without mapping those CVEs to the individual findings. The researcher describes four exploit chains: one XXE chain is said to require no credentials and run commands as the nable account, while two other chains reach root; the MMS3 chain requires an administrator to view poisoned patch details. Reports describe scanning and attempts against honeypots or decoys, but no confirmed customer-server compromise as of November 10. On-premises customers should upgrade servers, then Agents before Probes; N-able upgraded hosted servers, while hosted customers still upgrade their Agents and Probes. Until an on-premises server is upgraded, N-able recommends keeping it offline. Hotfix 2 removes legacy MDM and temporarily disables built-in remote control; Take Control continues to work. N-able says a follow-up hotfix will provide further security updates.

### Source excerpt

N-able released a hotfix for N-central that fixes seven CVEs after a researcher published proof-of-concept code for 33 alleged zero-day vulnerabilities. The researcher says one attack chain needs no credentials. Key Takeaways Able2Shell is a set of 33 alleged vulnerabilities in N-able N-central, published with proof-of-concept code. The researcher says one chain lets an unauthenticated attacker run commands on the server. Security firms report exploitation attempts against N-central honeypots, but as of November 10, no confirmed compromise of a customer server has been reported. N-able released N-central 2026.4 Hotfix 2 on November 10. It fixes seven CVEs. Background Tenable's Research Special Operations (RSO) team has compiled this blog to answer Frequently Asked Questions (FAQ) regarding Able2Shell, a set of reported zero-day vulnerabilities in N-able N-central. FAQ When was Able2Shell first disclosed? A researcher operating under the GitHub account "Oracle-Security" published a write-up titled "Able2Shell" in the account's CVEs repository. It describes 33 alleged N-central vulnerabilities with proof-of-concept code. The earliest README commit is dated November 9, 2026 at 04:14 UTC. N-able described the release as a public disclosure by an independent security researcher. N-able does not state whether it was notified in advance and does not name the researcher. What are the vulnerabilities associated with Able2Shell? On November 10, N-able published seven CVE records for vulnerabilities fixed in N-central 2026.4 Hotfix 2. On its status page, N-able says the release addresses "the most critical November 9 vulnerabilities" and that a follow-up hotfix will provide further security updates. The page lists all seven as related CVEs. One, CVE-2026-91000, had been reserved on September 14, before the public Able2Shell disclosure. CVEDescription (per N-able)CVSSv4CVE-2026-125883Multiple XML external entity (XXE) vulnerabilities9.3CVE-2026-125881Schema-hint server-side req

## Microsoft's November 2026 Patch Tuesday addresses 1093 CVEs (CVE-2026-124194)

DevFeed: [Microsoft's November 2026 Patch Tuesday addresses 1093 CVEs (CVE-2026-124194)](<https://devfeed.tech/articles/microsoft-s-november-2026-patch-tuesday-addresses-1093-cves-cve-2026-124194-128941.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/microsoft-november-2026-patch-tuesday-addresses-1093-cves-cve-2026-124194>)

Author: Research Special Operations

Published: 2026-11-10T19:01:34Z

Content type: news

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [Microsoft](<https://devfeed.tech/topics/microsoft.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [active-directory](<https://devfeed.tech/tags/active-directory.md>), [advanced](<https://devfeed.tech/tags/advanced.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [can](<https://devfeed.tech/tags/can.md>), [claude](<https://devfeed.tech/tags/claude.md>), [code](<https://devfeed.tech/tags/code.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [components](<https://devfeed.tech/tags/components.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-124194](<https://devfeed.tech/tags/cve-2026-124194.md>), [cves](<https://devfeed.tech/tags/cves.md>), [directory](<https://devfeed.tech/tags/directory.md>), [discovery](<https://devfeed.tech/tags/discovery.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [november-2026](<https://devfeed.tech/tags/november-2026.md>), [patch](<https://devfeed.tech/tags/patch.md>), [patch-tuesday](<https://devfeed.tech/tags/patch-tuesday.md>)

### AI overview

Microsoft's November 2026 Patch Tuesday fixes 1,093 CVEs across 287 products and components: 63 critical, 1,029 important, and one moderate. Elevation of privilege accounts for 48.9% of the fixes, followed by remote code execution at 27.1%. The excerpt highlights five vulnerabilities: Outlook spoofing (CVE-2026-124194), rated moderate, was reportedly exploited as a zero-day; a crafted Office file could expose a target's NTLMv2 hash for impersonation. Critical Active Directory Domain Services, Exchange Server, and Schannel flaws could enable network code execution; their assessments say exploitation is more likely. A SharePoint Server privilege escalation is rated important, with exploitation assessed as less likely. The article recommends applying patches promptly and scanning for systems that remain unpatched.

### Source excerpt

63Critical 1029Important 1Moderate 0Low Microsoft addresses 1093 CVEs in the eleventh Patch Tuesday of 2026. Microsoft patched 1093 CVEs in its November 2026 Patch Tuesday release, with 63 rated critical, 1029 rated as important, and one rated as moderate. This month's update includes patches for 287 products and components. The following table lists the products with the most CVEs patched this month. A full list of patched products is available in the appendix. RankProductCVE Count1Microsoft Office Word652Microsoft Office Excel643SQL Server534Windows Advanced Rasterization Platform375Windows Installer366Windows Graphics Kernel357Windows Kernel288Microsoft Office SharePoint279Windows DNS2210 (Tie)Microsoft Office Outlook2010 (Tie)Windows Print Spooler Components20 Elevation of Privilege (EoP) vulnerabilities accounted for 48.9% of the vulnerabilities patched this month, followed by remote code execution (RCE) vulnerabilities at 27.1%. Moderate CVE-2026-124194 | Microsoft Outlook spoofing vulnerability CVE-2026-124194 is a spoofing vulnerability in Microsoft Outlook. It received a CVSSv3 score of 6.5 and is rated moderate. An attacker could exploit this vulnerability by convincing a target to open a crafted Microsoft Office file. Successful exploitation would allow an attacker to obtain the target's valid NTLMv2 hash, which can then be used to impersonate that user in follow-on attacks. According to Microsoft, this vulnerability was exploited in the wild as a zero-day. Additionally, the advisory credits this discovery to a security researcher that used Claude, the large language model (LLM) from Anthropic, though no specific version of Claude was noted in the advisory. Critical CVE-2026-118146 | Windows Active Directory Domain Services remote code execution vulnerability CVE-2026-118146 is an RCE vulnerability affecting Windows Active Directory Domain Services. It received a CVSSv3 score of 8.8 and is rated as critical. An authenticated attacker could exploit an inco

## U.S. urges critical infrastructure orgs to secure refrigeration systems ASAP after EU supermarket and blood bank attacks

DevFeed: [U.S. urges critical infrastructure orgs to secure refrigeration systems ASAP after EU supermarket and blood bank attacks](<https://devfeed.tech/articles/u-s-urges-critical-infrastructure-orgs-to-secure-refrigeration-systems-asap-after-eu-supermarket-and-blood-bank-attacks-125626.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/u-s-urges-critical-infrastructure-orgs-to-secure-refrigeration-systems-asap-after-eu>)

Author: Christopher Day

Published: 2026-11-09T22:00:00Z

Content type: news

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [Critical Infrastructure](<https://devfeed.tech/topics/critical-infrastructure.md>), [cybersecurity and infrastructure security agency](<https://devfeed.tech/topics/cybersecurity-and-infrastructure-security-agency.md>)

Tags: [agriculture](<https://devfeed.tech/tags/agriculture.md>), [blood](<https://devfeed.tech/tags/blood.md>), [cisa](<https://devfeed.tech/tags/cisa.md>), [controllers](<https://devfeed.tech/tags/controllers.md>), [critical-infrastructure](<https://devfeed.tech/tags/critical-infrastructure.md>), [cyber-attacks](<https://devfeed.tech/tags/cyber-attacks.md>), [fbi](<https://devfeed.tech/tags/fbi.md>), [fire](<https://devfeed.tech/tags/fire.md>), [food](<https://devfeed.tech/tags/food.md>), [healthcare](<https://devfeed.tech/tags/healthcare.md>), [ot](<https://devfeed.tech/tags/ot.md>), [passwords](<https://devfeed.tech/tags/passwords.md>), [refrigeration-systems](<https://devfeed.tech/tags/refrigeration-systems.md>), [remote-access](<https://devfeed.tech/tags/remote-access.md>), [supermarket](<https://devfeed.tech/tags/supermarket.md>), [temperature](<https://devfeed.tech/tags/temperature.md>), [transportation](<https://devfeed.tech/tags/transportation.md>)

### AI overview

Following attacks on French blood banks and European supermarkets, U.S. agencies warn that remotely accessible refrigeration controllers are being targeted through unpatched flaws, misconfigurations, and weak or hard-coded passwords. Attackers can manipulate temperatures, spoiling food or blood and potentially triggering fires. The agencies recommend strong authentication and changed default passwords, prompt patching, replacement of end-of-life devices, identifying internet-accessible systems, isolating OT from business networks, removing unnecessary remote access, securing necessary access, and keeping offsite backups. French authorities reportedly identified compromises involving Danfoss AK-SM and AK-SC, Copeland, and Dixell XWEB controllers. The supplied text also describes Tenable One capabilities for asset discovery, OT inventory, attack-path visualization, and risk prioritization; these are vendor claims.

### Source excerpt

Following recent cyber attacks on French blood banks and European supermarkets, U.S. federal agencies are urging critical infrastructure organizations to immediately secure industrial refrigeration systems against remote tampering and temperature manipulation. Key takeaways Cybercriminals are actively targeting unpatched flaws, misconfigurations, and weak or hard-coded passwords in commercial cold-chain and refrigeration controllers globally. Attackers are gaining remote access to manipulate temperature controls and spoil essential products, such as blood and food. CISA, the FBI, and other U.S. agencies are advising organizations to isolate OT systems, secure or remove remote access, patch critical vulnerabilities, and replace end-of-life devices. Critical infrastructure organizations in the healthcare, chemicals, transportation, and food and agriculture sectors must urgently harden their industrial refrigeration and cold-chain monitoring systems to protect food, medicines, and other essential products against ongoing cyber attacks. That's the call from the U.S. Cybersecurity and Infrastructure Security Agency (CISA) and other U.S. government agencies, following a series of alarming breaches against refrigeration systems in French blood banks and European supermarkets. "Every organization that depends on refrigeration and monitoring systems should assume it could be a target," CISA Acting Executive Assistant Director for Cybersecurity Chris Butera said in a statement. Attackers are remotely targeting electronic-temperature and commercial-refrigeration controllers used in grocery stores and cold storage facilities. They're looking for unpatched vulnerabilities and other security flaws, such as misconfigurations, according to the agencies. Once attackers gain remote access to these systems, they try to tamper with these machines' temperature controls to damage their refrigerated products. The temperature changes could also trigger fire hazards. In a joint fact sheet,

## php2shell one week later: Why one exploit doesn't work everywhere

DevFeed: [php2shell one week later: Why one exploit doesn't work everywhere](<https://devfeed.tech/articles/php2shell-one-week-later-why-one-exploit-doesn-t-work-everywhere-107160.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/php2shell-one-week-later-why-one-exploit-doesnt-work-everywhere>)

Author: Joshua Martinelle, Thomas Cappetta

Published: 2026-10-30T01:42:06Z

Content type: news

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [CVE-2021-44228](<https://devfeed.tech/topics/cve-2021-44228.md>), [exploit chaining](<https://devfeed.tech/topics/exploit-chaining.md>)

Tags: [appliances](<https://devfeed.tech/tags/appliances.md>), [build](<https://devfeed.tech/tags/build.md>), [code](<https://devfeed.tech/tags/code.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [exploits](<https://devfeed.tech/tags/exploits.md>), [honeypots](<https://devfeed.tech/tags/honeypots.md>), [interfaces](<https://devfeed.tech/tags/interfaces.md>), [internet](<https://devfeed.tech/tags/internet.md>), [memory-handling](<https://devfeed.tech/tags/memory-handling.md>), [network-appliances](<https://devfeed.tech/tags/network-appliances.md>), [online](<https://devfeed.tech/tags/online.md>), [out-of-memory](<https://devfeed.tech/tags/out-of-memory.md>), [patch](<https://devfeed.tech/tags/patch.md>), [php](<https://devfeed.tech/tags/php.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [scanning](<https://devfeed.tech/tags/scanning.md>)

### AI overview

Tenable's week of testing found that php2shell can enable remote code execution, but exploitation generally requires tuning to the target's PHP build, SAPI, extensions, and runtime configuration. Five exposed vulnerable sites saw exploitation attempts but no compromise; successful execution was reported on researcher honeypots and network appliances. Public probes can misclassify systems: version matches do not prove exploitability, and stateful checks may miss vulnerable hosts or flag patched ones. Checks also depend on memory limits and worker reuse, and can crash workers. Shared-build appliances are a key exception because one tuned exploit may reach many devices. Prioritize patching or isolating internet-facing management interfaces, network appliances, and end-of-life PHP systems; use vendor fixes for appliances. Update PHP to fixed releases or distribution packages, and apply mitigations while upgrading legacy branches.

### Source excerpt

php2shell raised fears of mass exploitation. A week of testing by our research team found that working exploits had to be fitted to each target's exact PHP setup. Systems that share one build, such as network appliances, are the exception: one tuned exploit can reach every device that runs it. Key takeaways The five vulnerable PHP sites we exposed to the internet were not compromised, and public proofs-of-concept (PoCs) that go beyond version checks do not reliably confirm whether a host is vulnerable. Exploitation has been confirmed elsewhere, on researcher honeypots and on some network appliances. In realistic environments, turning php2shell into remote code execution usually takes an exploit built for the specific target. That is hard, not impossible, and it puts php2shell in a different category from Log4Shell, even though both received near-maximum severity ratings. Where many systems share one build, such as network appliances, a single calibrated exploit can work against all of them. Patch now, starting with internet-facing management interfaces, network appliances, and end-of-life PHP branches. Tenable Nessus and Tenable One Web App Scanning have had version-based detection since October 21. Background On October 20, 2026, PHP announced two vulnerabilities, and on October 21 released fixes for flaws that can allow unauthenticated remote code execution. CVE-2026-109618 is an out-of-memory handling flaw. CVE-2026-109619 is a use-after-free flaw caused by stale state shared between requests on the same worker. Each has a CVSSv4 score of 9.2. For a full breakdown of affected versions, fixes and mitigations, see our frequently asked questions blog post. This post covers what happened after the disclosure, based on what our team observed directly. From disclosure to headline in under 48 hours php2shell got big fast. Details of the vulnerabilities leaked online before the official release. Within two days, the vulnerability had a name, a logo and coverage in mainst

## Whole-of-state defense: How SLED agencies can secure critical infrastructure in the AI era

DevFeed: [Whole-of-state defense: How SLED agencies can secure critical infrastructure in the AI era](<https://devfeed.tech/articles/whole-of-state-defense-how-sled-agencies-can-secure-critical-infrastructure-in-the-ai-era-102581.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/whole-of-state-security-sled-critical-infrastructure>)

Author: Christopher Day

Published: 2026-10-27T13:00:00Z

Content type: article

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [shadow AI](<https://devfeed.tech/topics/shadow-ai.md>), [cybersecurity and infrastructure security agency](<https://devfeed.tech/topics/cybersecurity-and-infrastructure-security-agency.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-automation](<https://devfeed.tech/tags/ai-automation.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [applications](<https://devfeed.tech/tags/applications.md>), [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [critical-infrastructure](<https://devfeed.tech/tags/critical-infrastructure.md>), [cyber](<https://devfeed.tech/tags/cyber.md>), [cyberattacks](<https://devfeed.tech/tags/cyberattacks.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [governance](<https://devfeed.tech/tags/governance.md>), [reconnaissance](<https://devfeed.tech/tags/reconnaissance.md>), [speed](<https://devfeed.tech/tags/speed.md>)

### AI overview

The article argues that AI is widening SLED agencies' attack surface as staff adopt unapproved AI tools and applications, vendors add AI features and connectors, and attackers automate reconnaissance. Under-resourced local utilities, schools and other operators--with aging OT, remote access and unclear incident responsibilities--can provide routes toward larger systems, with risks to public services. It recommends a whole-of-state model that treats state and local entities as a shared defensive perimeter, built on clear governance, shared asset and exposure visibility, shared services, and trusted information sharing. Suggested steps include inventorying critical infrastructure and AI assets, prioritizing exploitable exposures by public-safety impact, securing exposed controllers and remote access, setting AI policies and approved-tool lists, and checking SLCGP funding availability. Tenable presents its products as providing unified IT, OT, cloud, identity and AI visibility; the article also notes that no single tool or jurisdiction solves the problem.

### Source excerpt

AI is widening the attack surface of the critical infrastructure facilities and services that state, local, and education (SLED) organizations run. In the final post of our Cybersecurity Awareness Month series, we explain how a whole-of-state security approach can help SLED agencies protect their critical infrastructure. Key takeaways Because cyber attackers prey on under-resourced targets, they often go after SLED organizations, especially those that operate critical infrastructure, including water systems, hospitals, mass transit, emergency services, and schools. In the latest research from the National Association of State Chief Information Officers (NASCIO), nearly 90% of state CIOs rated cyberattacks on critical systems as a high concern. AI expands the attack surface in two fundamental ways: SLED agencies and employees adopt AI tools and AI-built apps faster than security teams can authorize and inventory them, while attackers use AI automation to find weak points faster. A whole-of-state cybersecurity approach treats state agencies, counties, cities, school districts, and utilities as one defensive perimeter, with shared visibility, shared services, and clear governance. Cyber attackers often look for the weakest link that can offer them an entry point into larger targets. If they can't crack a state agency's hardened systems, they'll try to breach it in a roundabout way by first breaking into a small town's water utility, a rural school district, or a county dispatch center, and then attempt to move laterally toward the bigger target. When one of those weak links fails, the consequences can reach well beyond the breached agency: halted 911 dispatches, disrupted water service, exposed resident data, and more. AI is further complicating the picture. State, local, and education (SLED) organizations are adopting AI quickly to improve efficiency, employees are building applications with it informally, and adversaries are using it to speed up reconnaissance. Each

## Brotli2Shell: Frequently asked questions for Google Brotli decoder vulnerability (CVE-2026-111497)

DevFeed: [Brotli2Shell: Frequently asked questions for Google Brotli decoder vulnerability (CVE-2026-111497)](<https://devfeed.tech/articles/brotli2shell-frequently-asked-questions-for-google-brotli-decoder-vulnerability-cve-2026-111497-102579.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/brotli2shell-frequently-asked-questions-for-google-brotli-decoder-cve-2026-111497>)

Author: Satnam Narang

Published: 2026-10-27T01:19:40Z

Content type: article

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [CVSS v4.0](<https://devfeed.tech/topics/cvss-v4-0.md>), [releases](<https://devfeed.tech/topics/releases.md>), [NVD](<https://devfeed.tech/topics/nvd.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [apache-arrow](<https://devfeed.tech/tags/apache-arrow.md>), [brotli](<https://devfeed.tech/tags/brotli.md>), [brotli-decoder](<https://devfeed.tech/tags/brotli-decoder.md>), [bun](<https://devfeed.tech/tags/bun.md>), [clickhouse](<https://devfeed.tech/tags/clickhouse.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [compression](<https://devfeed.tech/tags/compression.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-111497](<https://devfeed.tech/tags/cve-2026-111497.md>), [envoy](<https://devfeed.tech/tags/envoy.md>), [envoy-proxy](<https://devfeed.tech/tags/envoy-proxy.md>), [ffmpeg](<https://devfeed.tech/tags/ffmpeg.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [google-s](<https://devfeed.tech/tags/google-s.md>), [http](<https://devfeed.tech/tags/http.md>), [http2shell](<https://devfeed.tech/tags/http2shell.md>), [istio](<https://devfeed.tech/tags/istio.md>), [net](<https://devfeed.tech/tags/net.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

CVE-2026-111497 ("Brotli2Shell") is an out-of-bounds write in Google's Brotli decoder; crafted Brotli data can cause a crash, memory disclosure, or potentially remote code execution. Exposure depends on whether a vulnerable decoder processes attacker-controlled data, including compressed HTTP traffic or files. A system Brotli update helps programs that use it after restart; products with bundled decoders need their own fixed releases. The excerpt lists fixes across major runtimes and libraries, but says ClickHouse had not shipped its merged fix and the Apache Arrow issue remained open as of October 26. Temporary measures include blocking incoming `Content-Encoding: br`, disabling decoding where applicable, or removing affected Python packages. These steps have limits: blocking inbound compressed requests does not protect clients fetching hostile responses, and disabling an intermediary decoder may pass compressed data to vulnerable downstream services.

### Source excerpt

Researchers have demonstrated remote code execution through CVE-2026-111497, an out-of-bounds write in Google's Brotli decoder library, and public proofs-of-concept (PoCs) are available. Software that uses the decoder includes Node.js, .NET, Bun, Envoy Proxy, Istio, Python HTTP clients and PHP for Windows. Key Takeaways CVE-2026-111497, known as Brotli2Shell and by several other names, is an out-of-bounds write in Google's Brotli decoder library that Google, the CVE Numbering Authority (CNA), scored 9.2 under CVSSv4.0. Any application that decompresses attacker-controlled data with a vulnerable Brotli decoder is potentially at risk, including Node.js, .NET, Bun, Envoy Proxy, Istio, Python HTTP clients, FFmpeg, Apache Arrow and ClickHouse. Patches are available for Google Brotli and the major runtimes, though some projects had not shipped a fixed release as of October 26, and applications that bundle their own copy of Brotli each need their own fix. Background Tenable's Research Special Operations (RSO) team has compiled this blog to answer Frequently Asked Questions (FAQ) regarding Brotli2Shell, a vulnerability in Google's Brotli C decoder library, which Node.js, .NET and other software embed. FAQ What is Brotli2Shell? Brotli2Shell is one of several names for CVE-2026-111497, a memory corruption flaw in Google's open-source Brotli compression library. Some researchers call it Node2Shell, after Node.js, which disclosed the flaw in its October 21 security advisory. Others use HTTP2Shell, since the same bug reaches HTTP software outside Node.js. It has circulated as Broccoli2Shell as well. We use Brotli2Shell because the bug sits in the Brotli decoder itself, not in any one downstream product. What is the vulnerability associated with Brotli2Shell? CVE-2026-111497 is an out-of-bounds write vulnerability in the Google Brotli C decoder library. CVEDescriptionCVSSv4.0CVE-2026-111497Google Brotli decoder out-of-bounds write vulnerability9.2 An attacker can trigger the flaw

## Discover and remediate PHP2Shell exposure with Tenable

DevFeed: [Discover and remediate PHP2Shell exposure with Tenable](<https://devfeed.tech/articles/discover-and-remediate-php2shell-exposure-with-tenable-102580.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/discover-and-remediate-php2shell-exposure-with-tenable>)

Author: Team Tenable

Published: 2026-10-26T19:48:07Z

Content type: tutorial

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Exposure Management](<https://devfeed.tech/topics/exposure-management.md>), [auto remediation](<https://devfeed.tech/topics/auto-remediation.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [generative-ai-tools](<https://devfeed.tech/topics/generative-ai-tools.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>)

Tags: [applications](<https://devfeed.tech/tags/applications.md>), [asm](<https://devfeed.tech/tags/asm.md>), [attack-surface-management](<https://devfeed.tech/tags/attack-surface-management.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-distribution](<https://devfeed.tech/tags/linux-distribution.md>), [patch](<https://devfeed.tech/tags/patch.md>), [patch-management](<https://devfeed.tech/tags/patch-management.md>), [patches](<https://devfeed.tech/tags/patches.md>), [php](<https://devfeed.tech/tags/php.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [remediation](<https://devfeed.tech/tags/remediation.md>), [tenable](<https://devfeed.tech/tags/tenable.md>), [tenable-one](<https://devfeed.tech/tags/tenable-one.md>)

### AI overview

The excerpt outlines how Tenable products can help teams find and remediate PHP2Shell (CVE-2026-109618 and CVE-2026-109619). Attack Surface Management discovers external PHP assets and monitors changes; Vulnerability Management and Security Center detect affected PHP, including Linux distribution packages. Cloud Vulnerability Management updates plugin feeds by default, while offline or air-gapped Security Center environments may need manual updates. Web App Scanning can assess PHP components when all plugin groups are selected, though these scans take longer and need known targets; ASM findings can add unknown apps to scope. Patch Management maps exposures to patches, launches workflows, and supports post-deployment validation. Cloud Exposure covers cloud workloads, while Tenable Hexa AI can help find vulnerable assets, create initiatives, and generate remediation tickets. The excerpt recommends updating PHP to fixed versions but does not specify those versions.

### Source excerpt

Learn how to use Tenable solutions to find vulnerable PHP versions, prioritize remediation, and patch the critical PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619) faster. Key takeaways The PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619) put security teams in a race against attackers. PHP runs on more than 70% of websites, so organizations need to quickly find where they're affected and update PHP to fixed versions. Tenable helps you find PHP2Shell across your attack surface. Tenable One Attack Surface Management discovers externally facing PHP assets. Tenable One Vulnerability Management and Tenable Security Center provide detections, including local checks for Linux distribution packages. Tenable One Web App Scanning assesses web applications, and Tenable One Cloud Exposure covers cloud workloads. Tenable accelerates remediation. Tenable Patch Management matches exposures to the right patches, launches patch workflows, and validates fixes with post-scan checks. Tenable One with Tenable Hexa AI lets you find vulnerable assets, create exposure initiatives, and generate remediation tickets with simple prompts. Respond faster with Tenable solutions The recently disclosed PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619) have put security teams in a race against attackers to remediate or mitigate exposure before their systems are targeted. PHP runs on more than 70% of websites, and many of those sites run unsupported, legacy branches that no longer receive upstream support. Organizations need to quickly find where they're affected and update PHP to fixed versions. To help cybersecurity teams accelerate emergency response, this blog outlines tips for using the Tenable solutions to identify vulnerable versions of PHP, prioritize remediation decisions, and implement patches as quickly as possible. External Attack Surface Management Tenable One Attack Surface Management (ASM) helps you discover externally facing assets running P

## The adversary economy: How threat actors are reacting to PHP2Shell

DevFeed: [The adversary economy: How threat actors are reacting to PHP2Shell](<https://devfeed.tech/articles/the-adversary-economy-how-threat-actors-are-reacting-to-php2shell-96384.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/php2shell-vulnerability-threat-actor-response>)

Author: Raymond Carney

Published: 2026-10-22T22:04:00Z

Content type: news

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [Threat Research](<https://devfeed.tech/topics/threat-research.md>), [Exposure Management](<https://devfeed.tech/topics/exposure-management.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [Cybercrime](<https://devfeed.tech/topics/cybercrime.md>), [Disaster Recovery](<https://devfeed.tech/topics/disaster-recovery.md>)

Tags: [adversary](<https://devfeed.tech/tags/adversary.md>), [ai](<https://devfeed.tech/tags/ai.md>), [business-continuity](<https://devfeed.tech/tags/business-continuity.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [cvss-v4-0](<https://devfeed.tech/tags/cvss-v4-0.md>), [dark-web](<https://devfeed.tech/tags/dark-web.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [exposure-management](<https://devfeed.tech/tags/exposure-management.md>), [forum](<https://devfeed.tech/tags/forum.md>), [forums](<https://devfeed.tech/tags/forums.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [law-enforcement](<https://devfeed.tech/tags/law-enforcement.md>), [migration](<https://devfeed.tech/tags/migration.md>), [patching](<https://devfeed.tech/tags/patching.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>)

### AI overview

After disclosure of two critical unauthenticated PHP vulnerabilities on Oct. 20, 2026, several criminal forums reportedly went offline, migrated infrastructure, restricted registrations, or moved communications to Telegram. The article says operators feared both law enforcement and rival groups could exploit forums holding identities, messages, transaction records, and stolen credentials; the 2024 BreachForums seizure had reinforced infrastructure risk. It also reports private-channel exploit circulation and pre-disclosure activity, while warning that AI-assisted research may shorten the time to weaponization. For defenders, it recommends prioritizing CVE-2026-109618 and CVE-2026-109619: versions below PHP 8.3 are affected, and end-of-life branches receive no patches, so upgrade is the stated remediation. Where immediate upgrading is infeasible, it suggests web application firewalls, network segmentation, and enhanced monitoring.

### Source excerpt

Two critical PHP vulnerabilities sent criminal forum operators scrambling to protect their own infrastructure, revealing that threat actors face the same exposure management challenges as the organizations they target. Key takeaways The adversary economy operates on the same fundamental principles as the legitimate economy. Forum self-evacuations: Criminal forums including BreachForums initiated emergency infrastructure migrations, taking themselves offline within hours of PHP2Shell disclosure, citing direct risk to their operations. Underground operators face a dual threat: both law enforcement and rival criminal groups could weaponize PHP2Shell against forum infrastructure storing member identities, private communications, and stolen credentials. The adversary response mirrors legitimate enterprise incident response, including emergency patching, platform migration, and business continuity planning. Historical precedent from the 2024 BreachForums seizure conditioned criminal operators to treat infrastructure vulnerabilities as existential business risks Background PHP powers an estimated 75% of websites with identifiable server-side technology, making it the backbone of the modern web. That infrastructure extends far beyond legitimate businesses. Criminal forums, dark web marketplaces, and underground communication platforms rely on the same PHP-based software stacks, such as phpBB, custom forum engines, and web-based administration panels, that power their legitimate counterparts. On Oct. 20, 2026, two critical unauthenticated remote code execution vulnerabilities in PHP were publicly disclosed: CVE-2026-109618 (OOM Corruption) and CVE-2026-109619 (Stale Global State), each carrying a CVSS v4.0 score of 9.2. The two flaws target different stages of PHP's memory management, and chaining them together yields a more reliable exploitation path than either alone. Researchers credit frontier AI models with both the initial discovery and the exploitation chain connectin

## How to contain shadow AI, as it takes on multiple forms and spreads throughout your environment

DevFeed: [How to contain shadow AI, as it takes on multiple forms and spreads throughout your environment](<https://devfeed.tech/articles/how-to-contain-shadow-ai-as-it-takes-on-multiple-forms-and-spreads-throughout-your-environment-95438.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/how-to-contain-shadow-ai-as-it-takes-on-multiple-forms-and-spreads-throughout-your-environment>)

Author: Robert Huber

Published: 2026-10-22T13:00:00Z

Content type: article

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [shadow AI](<https://devfeed.tech/topics/shadow-ai.md>), [Exposure Management](<https://devfeed.tech/topics/exposure-management.md>)

Tags: [acceptable-use](<https://devfeed.tech/tags/acceptable-use.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-assistant](<https://devfeed.tech/tags/ai-assistant.md>), [ai-chatbot](<https://devfeed.tech/tags/ai-chatbot.md>), [ai-chatbots](<https://devfeed.tech/tags/ai-chatbots.md>), [ai-coding-assistants](<https://devfeed.tech/tags/ai-coding-assistants.md>), [ai-model](<https://devfeed.tech/tags/ai-model.md>), [ai-tool](<https://devfeed.tech/tags/ai-tool.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [asset](<https://devfeed.tech/tags/asset.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [autonomous-agents](<https://devfeed.tech/tags/autonomous-agents.md>), [awareness](<https://devfeed.tech/tags/awareness.md>), [awareness-training](<https://devfeed.tech/tags/awareness-training.md>), [blog](<https://devfeed.tech/tags/blog.md>), [contain](<https://devfeed.tech/tags/contain.md>), [multiple](<https://devfeed.tech/tags/multiple.md>), [shadow-ai](<https://devfeed.tech/tags/shadow-ai.md>)

### AI overview

Shadow AI now includes MCP servers, browser extensions, local models, coding assistants, agents, and other assets that can expose sensitive data or create security blind spots. The article recommends three steps: train employees to recognize risks and give security teams a way to understand why unsanctioned tools are used; set a living acceptable-use policy with approved tools, data-handling rules, accountability, and a review process; and include AI assets in unified exposure management. The latter means inventorying assets and access, finding flaws and excessive permissions, prioritizing risks in business context, and monitoring data flows to detect or block sensitive information. The article cautions that default blocking can push use underground. Its examples and cited statistics illustrate the risks, but the supplied excerpt does not establish that the listed measures eliminate them.

### Source excerpt

Shadow AI used to be confined to a few simple scenarios, such as AI chatbots and AI browser extensions. Today, it spans a broad spectrum of complex vectors, making it harder to detect and control. In the latest installment of our Cybersecurity Awareness Month blog series, learn how employee security training, AI usage governance, and exposure management can help you tackle shadow AI successfully. Key takeaways Integrating shadow AI into security awareness training helps employees recognize its risks and learn how to safely adopt AI tools. Security teams should foster open communication with employees and try to understand why they use unsanctioned AI products. Shadow AI now spans local models, AI coding assistants, autonomous agents, and many other asset types across your environment, making it a pervasive and complex problem. You can reduce shadow AI incidence by enacting an AI acceptable use policy that provides clear guidelines and a list of approved AI tools, and by addressing shadow AI as part of your unified exposure management program. It's an ordinary workday at a typical mid-to-large enterprise, and the following is happening without the knowledge of the IT and security departments: A marketing manager installs an unvetted, open-source Model Context Protocol (MCP) server to secretly bridge his desktop AI assistant with the company's internal customer database. A sales executive downloads a free AI browser extension to summarize a web page, unknowingly granting a third party read-access to her confidential CRM dashboards. An accounting supervisor creates custom AI chatbot skills to automate his reporting, feeding unredacted financial projections into a public generative AI tool. An engineer bypasses software restrictions to download and run an unvetted, locally hosted AI model, creating a massive blind spot for endpoint security. A business analyst hands over his broad administrative credentials to a consumer-grade AI agent so it can autonomously crawl the c

## How Tenable brought multi-language support to security detectors with agentic translation

DevFeed: [How Tenable brought multi-language support to security detectors with agentic translation](<https://devfeed.tech/articles/how-tenable-brought-multi-language-support-to-security-detectors-with-agentic-translation-92859.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/how-tenable-brought-multi-language-support-to-security-detectors-with-agentic-translation>)

Author: Aviad Moreshet

Published: 2026-10-21T13:00:00Z

Content type: article

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [LLM security](<https://devfeed.tech/topics/llm-security.md>), [machine-translation](<https://devfeed.tech/topics/machine-translation.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-security](<https://devfeed.tech/tags/ai-security.md>), [arabic](<https://devfeed.tech/tags/arabic.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [content](<https://devfeed.tech/tags/content.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [detection](<https://devfeed.tech/tags/detection.md>), [english](<https://devfeed.tech/tags/english.md>), [fallback](<https://devfeed.tech/tags/fallback.md>), [faster](<https://devfeed.tech/tags/faster.md>), [gate](<https://devfeed.tech/tags/gate.md>), [language](<https://devfeed.tech/tags/language.md>), [language-support](<https://devfeed.tech/tags/language-support.md>), [security](<https://devfeed.tech/tags/security.md>), [tenable](<https://devfeed.tech/tags/tenable.md>), [translation](<https://devfeed.tech/tags/translation.md>)

### AI overview

Tenable replaced its per-request translate-then-detect flow with a compact multilingual detector fine-tuned on label-preserving data produced by an agentic pipeline. A frontier LLM transcreates each item using its label and target language; independent judges check fluency, meaning, and label integrity, with refinement for failed items and a controlled open-source model fallback for refusals. The detector runs natively in 10 formally supported languages, with reported detection 20-800 times faster per item and a 12-14x smaller memory footprint than the prior flow. Tenable reports a one-time data-generation cost under $10,000 that does not scale with customer traffic, and no English performance regression. It reports matching or better recall than translate-then-detect on 9 of 10 languages for AI-threat detection and on every language for harmful-content detection. Although the pretrained model can read and flag attacks in many untrained languages, Tenable says only the 10 supported languages have been formally validated.

### Source excerpt

AI security tools that can only detect threats in English offer limited protection. Here's how Tenable trained our threat detectors to process nine additional languages and understand thousands more, without the need for a translation model, which increases costs and slows down processing. Key takeaways Tenable One AI Exposure's detectors, covering AI threats, harmful content, and other policy risks, were originally English-centric. To assess threats written in other languages, our product translated them into English, a slow, expensive, and often imprecise approach. Tenable built an agentic translation pipeline that generates high-fidelity, label-preserving training and benchmark data across nine languages, guarded by a multi-judge quality gate, a refinement loop, and a model-refusal handling fallback. This single multilingual model detects threats natively in all 10 supported languages. Compared with our previous process of translating threats into English, this model is roughly 20-800 times faster per item and is less expensive by an order of magnitude, bearing a one-time cost that does not grow with usage traffic from our customers. Why your AI security tool should support multiple languages A prompt attack against an AI model written in Spanish, Arabic, or Hindi is every bit as dangerous as one written in English, which is why an English-only AI security detector will leave your organization at risk from non-English attacks. To address this issue in our product, Tenable first adopted a "translate-then-detect" process: Identify the language. Translate the input to English with a large translation model. Then run the English detector. This process works, but it has four downsides: Latency. A large, autoregressive translation model that runs before every non-English detection needs hundreds of milliseconds for short inputs, and seconds to tens of seconds for long ones. Cost. Every non-English request pays for a full translation pass. Operational overhead. You have

## php2shell (CVE-2026-109618, CVE-2026-109619): Frequently asked questions about critical PHP remote code execution vulnerabilities

DevFeed: [php2shell (CVE-2026-109618, CVE-2026-109619): Frequently asked questions about critical PHP remote code execution vulnerabilities](<https://devfeed.tech/articles/php2shell-cve-2026-109618-cve-2026-109619-frequently-asked-questions-about-critical-php-remote-code-execution-vulnerabilities-92578.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/php2shell-cve-2026-109618-cve-2026-109619-frequently-asked-questions-about-critical-php-remote>)

Author: Satnam Narang

Published: 2026-10-21T09:01:24Z

Content type: article

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [code security](<https://devfeed.tech/topics/code-security.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [cves](<https://devfeed.tech/tags/cves.md>), [dane-knecht](<https://devfeed.tech/tags/dane-knecht.md>), [emergency](<https://devfeed.tech/tags/emergency.md>), [end-of-life](<https://devfeed.tech/tags/end-of-life.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [exploit-chain](<https://devfeed.tech/tags/exploit-chain.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [faq](<https://devfeed.tech/tags/faq.md>), [php](<https://devfeed.tech/tags/php.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [remote](<https://devfeed.tech/tags/remote.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

CVE-2026-109618 and CVE-2026-109619 are critical PHP vulnerabilities publicly described as remote code execution flaws; PHP rates each CVSSv4.0 9.2. The excerpt says technical details and official affected/fixed version lists were still pending, with patches scheduled for October 21, 2026 at 14:00 UTC. Reported fixed versions point to PHP 8.2-8.5 branches; end-of-life branches are not expected to receive official fixes, though Linux distributors may backport patches. Cloudflare reported early attacks and deployed WAF rules for known vectors as a temporary measure limited to traffic it routes. PHP developers say patching or upgrading is the only mitigation; CERT-EU recommends considering isolation of internet-facing applications when immediate patching is not feasible. Public exploit code was circulating but remained unverified in the excerpt.

### Source excerpt

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 evide

## Oracle October 2026 Critical Patch Update Addresses 1209 CVEs

DevFeed: [Oracle October 2026 Critical Patch Update Addresses 1209 CVEs](<https://devfeed.tech/articles/oracle-october-2026-critical-patch-update-addresses-1209-cves-91168.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/oracle-october-2026-critical-patch-update-addresses-1209-cves>)

Author: Research Special Operations

Published: 2026-10-20T21:58:58Z

Content type: news

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [enterprise data protection](<https://devfeed.tech/topics/enterprise-data-protection.md>), [Oracle Database](<https://devfeed.tech/topics/oracle-database.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cves](<https://devfeed.tech/tags/cves.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [fusion](<https://devfeed.tech/tags/fusion.md>), [middleware](<https://devfeed.tech/tags/middleware.md>), [october](<https://devfeed.tech/tags/october.md>), [october-2026](<https://devfeed.tech/tags/october-2026.md>), [oracle](<https://devfeed.tech/tags/oracle.md>), [oracle-fusion](<https://devfeed.tech/tags/oracle-fusion.md>), [patch](<https://devfeed.tech/tags/patch.md>), [patches](<https://devfeed.tech/tags/patches.md>), [security](<https://devfeed.tech/tags/security.md>), [security-patches](<https://devfeed.tech/tags/security-patches.md>), [security-updates](<https://devfeed.tech/tags/security-updates.md>), [update](<https://devfeed.tech/tags/update.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Oracle's October 2026 Critical Patch Update fixes 1,209 unique CVEs through 1,295 security updates across 33 product families. It includes 112 critical patches covering 95 CVEs; medium severity accounts for 47.3% of updates and high severity for 36.7%. Fusion Middleware has the most patches (206, 15.9%), followed by E-Business Suite (194, 15%). The excerpt's table also counts vulnerabilities exploitable over a network without authentication, including 134 for Fusion Middleware and 31 for E-Business Suite. Oracle customers are advised to apply all relevant patches and consult the October advisory for details.

### Source excerpt

Oracle addresses 1209 CVEs in its final quarterly update of 2026 with 1295 patches, including 112 critical updates. Key Takeaways The October 2026 Critical Patch Update (CPU) contains fixes for 1209 unique CVEs in 1295 security updates 112 issues (8.6% of all patches) were assigned a critical severity rating Oracle Fusion Middleware received the highest number of patches at 206, accounting for 15.9% of all patches Background On October 20, Oracle released its Critical Patch Update (CPU) for October 2026, the final quarterly update of the year. This CPU contains fixes for 1209 unique CVEs in 1295 security updates across 33 Oracle product families. Out of the 1295 security updates published this quarter, 8.6% of patches were assigned a critical severity. Medium severity patches accounted for the bulk of security patches at 47.3%, followed by high severity patches at 36.7%. This quarter's update includes 112 critical patches across 95 CVEs. SeverityIssues PatchedCVEsCritical11295High475439Medium613582Low9593Total12951209 Analysis This quarter, the Oracle Fusion Middleware product family contained the highest number of patches at 206, accounting for 15.9% of the total patches, followed by Oracle E-Business Suite at 194 patches, which accounted for 15% of the total patches. A full breakdown of the patches for this CPU can be seen in the following table, which also includes a count of vulnerabilities that can be exploited over a network without authentication. Oracle Product FamilyNumber of PatchesRemote Exploit without AuthOracle Fusion Middleware206134Oracle E-Business Suite19431Oracle Siebel CRM12266Oracle Communications11077Oracle PeopleSoft10941Oracle JD Edwards10244Oracle MySQL9829Oracle Java SE5549Oracle Supply Chain5019Oracle Essbase3814Oracle REST Data Services3511Oracle Analytics3314Oracle Systems289Oracle Database Server144Oracle Construction and Engineering137Oracle Enterprise Manager122Oracle GoldenGate113Oracle Trusted Answer Search81Oracle Utilities Applica

## Unmasking the robots: Why it's critical to discover AI agent identities and how Tenable helps you secure them

DevFeed: [Unmasking the robots: Why it's critical to discover AI agent identities and how Tenable helps you secure them](<https://devfeed.tech/articles/unmasking-the-robots-why-it-s-critical-to-discover-ai-agent-identities-and-how-tenable-helps-you-secure-them-90293.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/secure-ai-agent-identities-microsoft-entra-agent-id-tenable-one>)

Author: Clément Notin

Published: 2026-10-19T13:17:00Z

Content type: article

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [Next-Gen Identity Security](<https://devfeed.tech/topics/next-gen-identity-security.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [Use Cases for Every Cloud Service Model](<https://devfeed.tech/topics/use-cases-for-every-cloud-service-model.md>)

Tags: [agent-identities](<https://devfeed.tech/tags/agent-identities.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-identity-security](<https://devfeed.tech/tags/ai-identity-security.md>), [it](<https://devfeed.tech/tags/it.md>), [microsoft-entra](<https://devfeed.tech/tags/microsoft-entra.md>), [tenable](<https://devfeed.tech/tags/tenable.md>)

### AI overview

The article discusses the security risks of treating AI agents as ordinary non-human identities and describes Microsoft Entra Agent ID's identity model. It presents Tenable One Cloud Exposure as a way to discover and inventory these identities, with recommendations to avoid assigning agents human identities or over-privileged service accounts.

### Source excerpt

Discover how to secure AI agents in your cloud environment with Tenable One Cloud Exposure. We explore Microsoft Entra Agent ID and provide essential best practices for robust agentic AI identity security. Key takeaways Understand your current maturity level and then build an appropriate action plan to secure your agent identities. Use your cloud providers' native tools or Tenable One Cloud Exposure to locate and catalog every AI agent operating in your environment. Do not assign human identities or over-privileged service accounts to the AI agents your vendors deploy in your environment. Instead, require that vendors adopt official models like Microsoft Entra Agent ID for their AI agents' identities. As AI agents move from experimental toys to tools that make autonomous decisions, interact with databases, and call external APIs, organizations need to be clear on who -- or what -- is executing these actions in their cloud environments. Why non-human identities (NHIs) aren't secure enough for AI agents Security teams categorize identities into two buckets: human identities and non-human identities (NHIs), such as service accounts, secrets, and automated scripts. Treating AI agents as standard NHIs is a recipe for disaster. AI agents combine their non-deterministic nature with their ability to execute flexible, outcome-oriented actions, rather than following strict, prescribed instructions. Unlike classic, predictable scripts that follow rigid code paths, AI agents: Make creative, runtime decisions using LLMs. Interact with dynamic external tools, memory caches, and knowledge bases. Constantly adapt to solve problems, making it difficult for a security team to establish AI agents' baseline behavior. To address this challenge, major cloud providers have introduced dedicated, specialized agentic AI identity models. Let's break down one major model: Microsoft Entra Agent ID. Microsoft Entra Agent ID Feature / dimensionMicrosoft Entra Agent IDPrimary architectureIdentity pr

## Microsoft's October 2026 Patch Tuesday addresses 1407 CVEs (CVE-2026-96951)

DevFeed: [Microsoft's October 2026 Patch Tuesday addresses 1407 CVEs (CVE-2026-96951)](<https://devfeed.tech/articles/microsoft-s-october-2026-patch-tuesday-addresses-1407-cves-cve-2026-96951-86246.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/microsofts-october-2026-patch-tuesday-addresses-1407-cves-cve-2026-96951>)

Author: Research Special Operations

Published: 2026-10-13T21:49:11Z

Content type: news

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>), [DLL hijacking](<https://devfeed.tech/topics/dll-hijacking.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cves](<https://devfeed.tech/tags/cves.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [patch](<https://devfeed.tech/tags/patch.md>), [patch-tuesday](<https://devfeed.tech/tags/patch-tuesday.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [security](<https://devfeed.tech/tags/security.md>), [shell](<https://devfeed.tech/tags/shell.md>), [social-engineering](<https://devfeed.tech/tags/social-engineering.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

Microsoft's October 2026 Patch Tuesday release addresses 1,407 CVEs across 301 products and components, including two zero-day vulnerabilities, one exploited in the wild. The article highlights CVE-2026-96951, a Windows Shell security feature bypass that can be triggered by persuading a target to open a malicious file.

### Source excerpt

69Critical 1337Important 0Moderate 1Low Microsoft addresses 1407 CVEs in the tenth Patch Tuesday of 2026, marking the second consecutive month to reset the bar as the largest Patch Tuesday release. This month's updates include patches for two zero days, including one that was exploited in the wild. Microsoft patched 1,407 CVEs in its October 2026 Patch Tuesday release, with 69 rated critical, 1,337 rated as important, and one rated as low. This month's update includes patches for 301 products and components. The following table lists the products with the most CVEs patched this month. A full list of patched products is available in the appendix. RankProductCVE Count1Microsoft Office Excel692Role: DNS Server523Windows Kernel464Windows Installer385Windows Win32 Kernel Subsystem366Microsoft Office SharePoint347Microsoft Windows Search Component298Windows NTFS269.NET2510 (Tie)Microsoft Office Word2210 (Tie)SQL Server2210 (Tie)Windows Error Reporting22 Elevation of Privilege (EoP) vulnerabilities accounted for 47.9% of the vulnerabilities patched this month, followed by remote code execution (RCE) vulnerabilities at 22.3%. Important CVE-2026-96951 | Windows Shell security feature bypass vulnerability CVE-2026-96951 is a security feature bypass vulnerability affecting Windows Shell. It received a CVSSv3 score of 8.8 and was rated as important. According to Microsoft, this vulnerability was exploited in the wild as a zero-day. An attacker could exploit this vulnerability using social engineering tactics, via email or messages, to convince their target to open a malicious file. Successful exploitation would bypass the Mark of the Web (MOTW) security feature. This is the third flaw in Windows Shell that was exploited in the wild in 2026: CVE-2026-21510 was patched in February 2026's Patch Tuesday while CVE-2026-32202 was patched in April 2026's Patch Tuesday. Important CVE-2026-108398 |.NET Framework security feature bypass vulnerability CVE-2026-108398 is a security feature

## Critical infrastructure orgs face heightened cyber risk from nation-state groups, AI threats

DevFeed: [Critical infrastructure orgs face heightened cyber risk from nation-state groups, AI threats](<https://devfeed.tech/articles/critical-infrastructure-orgs-face-heightened-cyber-risk-from-nation-state-groups-ai-threats-86245.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/critical-infrastructure-orgs-face-heightened-cyber-risk-from-nation-state-groups-ai-threats>)

Author: Jamie Brown

Published: 2026-10-13T13:00:00Z

Content type: article

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [Critical Infrastructure](<https://devfeed.tech/topics/critical-infrastructure.md>), [AI in cybersecurity](<https://devfeed.tech/topics/ai-in-cybersecurity.md>), [cybersecurity and infrastructure security agency](<https://devfeed.tech/topics/cybersecurity-and-infrastructure-security-agency.md>)

### AI overview

The article examines nation-state and AI-assisted threats to critical infrastructure, emphasizing asset visibility gaps and vulnerable legacy OT systems. It summarizes CISA guidance on patching, replacing unsupported devices, securing network connections, monitoring activity, and preparing recovery plans. It also describes how attackers could use AI to map connected IT/OT environments and acquire specialized industrial-system knowledge.

### Source excerpt

Critical infrastructure faces mounting threats from nation-state groups and AI-driven attacks. In the latest installment of our Cybersecurity Awareness Month blog series, learn how leading cybersecurity agencies, such as CISA, are advising critical infrastructure organizations on ways to protect themselves and the essential services they provide. Key takeaways Critical infrastructure organizations often struggle with asset visibility gaps that create hidden attack vectors. Many older OT systems are difficult to inventory, leaving them unmonitored and unpatched. Attackers are leveraging AI to map converged IT/OT networks at machine speed and exploit uninventoried legacy systems. Attackers are also using AI to attain the specialized know-how to breach complex industrial control systems. Iran-affiliated APT groups have attacked U.S. water, energy, and government facilities since the U.S. launched Operation Epic Fury in February, according to the U.S. government. As part of Cybersecurity Awareness Month, CISA is urging critical infrastructure operators to establish a solid cyber hygiene foundation, anchored on reducing vulnerabilities, replacing unsupported legacy devices, and preparing rapid recovery plans. Cybersecurity Awareness Month 2026 finds critical infrastructure organizations facing a particularly daunting cyber risk landscape. Always a prime target for cybercriminals, hacktivists, and nation-state hacking groups, critical infrastructure organizations this year have been grappling with a heightened threat from adversaries affiliated with Iran's government, as documented by global cybersecurity agencies and researchers. Specifically, many of these nation-state groups have shifted their focus from stealthy cyber espionage activities to destructive cyber attacks designed to disrupt victims' operations, experts have observed. In addition, critical infrastructure organizations, which often must secure complex environments where IT and operational technology (OT) co

## Inside the Exchange Inspector: How Tenable uses OpenAI GPT cyber models to review open-source AI agents

DevFeed: [Inside the Exchange Inspector: How Tenable uses OpenAI GPT cyber models to review open-source AI agents](<https://devfeed.tech/articles/inside-the-exchange-inspector-how-tenable-uses-openai-gpt-cyber-models-to-review-open-source-ai-agents-77371.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/tenable-openai-security-vetting-open-source-ai-agents-exchange-inspector>)

Author: Robert McSulla

Published: 2026-10-08T12:50:00Z

Content type: article

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [ai security](<https://devfeed.tech/topics/ai-security.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [AI software supply chain security](<https://devfeed.tech/topics/ai-software-supply-chain-security.md>), [snyk-open-source](<https://devfeed.tech/topics/snyk-open-source.md>), [codex](<https://devfeed.tech/topics/codex.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [cyber](<https://devfeed.tech/tags/cyber.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [open-source-ai](<https://devfeed.tech/tags/open-source-ai.md>), [prompt-injection](<https://devfeed.tech/tags/prompt-injection.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Tenable's Exchange Inspector reviews community-built AI agents, skills, and MCP servers before they receive a vetted listing on the CyberAgents Exchange. The process combines automated screening, assessment with OpenAI GPT Cyber models, and human review with runtime verification, covering 15 security issue classes. The article also describes early vetted listings and reports efficiency results for security workflows.

### Source excerpt

Community-built AI agents, skills, and MCP servers are landing in SOC workflows fast. Here's what the Exchange Inspector tests before a listing earns its vetted tag on the CyberAgents Exchange. Three tools have already passed. Key takeaways Every Inspector-vetted listing clears three gates: an automated check, a frontier model assessment, and human verification. Tenable uses Tenable One AI Exposure to screen for prompt injection and exposed secrets, and OpenAI GPT Cyber models to assess the code and threat model. Tenable security researchers then verify runtime behavior in a clean environment. The review tests 15 types of security issues across three layers of the stack. These issues range from conventional flaws like SSRF and path traversal vulnerabilities to agent-specific ones like excessive permissions and memory poisoning. Vetted tools are driving efficiencies: SOC Hunter has cut hunt times by 75% for Tenable's security team. The CyberAgents Exchange currently has three Exchange Inspector-vetted listings: two built by Tenable and the other one by Splunk. These agents' contributors report that they accelerate threat hunting, remediation triage, and cloud posture investigation. Open by design, vetted before you deploy Security teams are increasingly deploying AI agents to triage alerts, correlate threat intelligence, investigate suspicious activity, and prioritize vulnerabilities across their environments. It's critical to know what these AI agents will do before you deploy them to a production environment. An agent carries credentials, calls tools, and acts on what it reads, so its blast radius is bigger than the one from a typical open-source library. Software supply chain attacks have taught us what happens when a registry trusts contributors by default. The CyberAgents Exchange, powered by Tenable, is an open-source, vendor-agnostic directory for security practitioners to discover, share, and deploy agentic AI. Contributors keep their code in their own public

## How to mitigate the risk from AI-generated apps built by your 'citizen coder' employees

DevFeed: [How to mitigate the risk from AI-generated apps built by your 'citizen coder' employees](<https://devfeed.tech/articles/how-to-mitigate-the-risk-from-ai-generated-apps-built-by-your-citizen-coder-employees-65701.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/how-to-secure-mitigate-ai-risk-vibe-coding-ai-apps-citizen-coders>)

Author: Phillip Hayes

Published: 2026-10-06T15:00:00Z

Content type: article

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [shadow AI](<https://devfeed.tech/topics/shadow-ai.md>), [ai-governance](<https://devfeed.tech/topics/ai-governance.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [AI software supply chain security](<https://devfeed.tech/topics/ai-software-supply-chain-security.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-generated-apps](<https://devfeed.tech/tags/ai-generated-apps.md>), [awareness-training](<https://devfeed.tech/tags/awareness-training.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [governance](<https://devfeed.tech/tags/governance.md>), [guardrails](<https://devfeed.tech/tags/guardrails.md>), [risk](<https://devfeed.tech/tags/risk.md>), [shadow-ai](<https://devfeed.tech/tags/shadow-ai.md>)

### AI overview

Tenable describes a five-tier governance framework for managing workplace applications built by nontechnical employees with AI tools. The framework combines company-wide policies, approved tools, departmental oversight, training, and peer support to address vulnerabilities, data protection, compliance, and the workload of reviewing a growing number of apps. The article argues that governance and training work better than blanket bans, which can drive app building out of sight.

### Source excerpt

AI tools let non-technical employees build workplace apps in minutes with natural language prompts. While these AI-generated apps boost productivity, they can create severe security and data risks. As Cybersecurity Awareness Month kicks off, we're sharing how Tenable adopted a structured governance framework that allows our "citizen coders" to build secure and compliant apps with AI. Key takeaways Unsanctioned applications that non-technical staff build using AI tools often bypass quality assurance and testing, creating shadow AI risks. Without IT and security oversight, these applications can go into use with critical vulnerabilities and misconfigurations, as well as weak data protection. Even when "citizen coders" comply with their organizations' policies and processes, the number of applications they build using AI tools can become overwhelming and disruptive for the IT and security teams. Governance works better than blanket bans, because prohibiting AI-aided development usually causes employees to keep their app development activities hidden. Tenable has found that implementing a structured, multi-tiered governance framework gives employee citizen coders the security and compliance guardrails they need. An effective governance framework should combine peer leadership and training. While AI leaders in each department are tasked with overseeing tool approvals, managing app dev request queues, and tracking applications' ROI, "citizen coders" should receive mandatory security and compliance awareness training. AI tools are making it easier than ever for non-technical employees to spin up workplace applications in minutes. Even staffers who have never written a single line of code, let alone set up a database, are jumping on the AI vibe-coding bandwagon, often encouraged by their team leaders First, the good news: These AI-generated applications can help boost employees' productivity by automating workflows and streamlining processes. And if employees can build thei

## Frequently asked questions about reported Citrix NetScaler zero-day vulnerabilities

DevFeed: [Frequently asked questions about reported Citrix NetScaler zero-day vulnerabilities](<https://devfeed.tech/articles/frequently-asked-questions-about-reported-citrix-netscaler-zero-day-vulnerabilities-60629.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/frequently-asked-questions-about-reported-citrix-netscaler-zero-day-vulnerabilities>)

Author: Satnam Narang

Published: 2026-09-27T09:35:21Z

Content type: news

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [code security](<https://devfeed.tech/topics/code-security.md>), [Security research](<https://devfeed.tech/topics/security-research.md>), [CVE-2026-58138](<https://devfeed.tech/topics/cve-2026-58138.md>)

Tags: [actively-exploited](<https://devfeed.tech/tags/actively-exploited.md>), [patch](<https://devfeed.tech/tags/patch.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [security](<https://devfeed.tech/tags/security.md>), [zero-day-vulnerabilities](<https://devfeed.tech/tags/zero-day-vulnerabilities.md>)

### AI overview

Citrix confirmed two actively exploited zero-day remote code execution vulnerabilities in NetScaler ADC and NetScaler Gateway and released patches on September 27, 2026. Tenable's FAQ summarizes the reports, bulletin updates, patch information, and indicators of compromise guidance.

### Source excerpt

CVE-2026-88771 and CVE-2026-88772, two zero-day vulnerabilities in Citrix NetScaler, have been confirmed as exploited in the wild. Citrix released patches on September 27, 2026. Change log Update September 27: Citrix published security bulletin CTX697096, confirming CVE-2026-88771 and CVE-2026-88772 as the two zero-day RCE vulnerabilities and releasing patches. Post updated with CVE IDs, CVSS scores, patch versions, and IoC guidance. Click here to review the change log history Update September 27: Citrix published security bulletin CTX697096, confirming CVE-2026-88771 and CVE-2026-88772 as the two zero-day RCE vulnerabilities and releasing patches. Post updated with CVE IDs, CVSS scores, patch versions, and IoC guidance. September 27: Original publication based on limited public information ahead of Citrix's official advisory. Key takeaways Citrix has confirmed two critical zero-day vulnerabilities in NetScaler ADC and NetScaler Gateway, both capable of remote code execution and actively exploited in the wild. Citrix released patches on September 27, 2026. Citrix says generic indicators of compromise will be available through NetScaler Console, and customers can request them from Citrix Support. Background Tenable's Research Special Operations (RSO) team has compiled this blog to answer Frequently Asked Questions (FAQ) regarding two reported zero-day vulnerabilities in Citrix NetScaler that sources say were actively exploited in the wild. The following FAQ is based on limited public information. This post was last updated on September 27, 2026 following publication of the official Citrix security bulletin. FAQ What is the source of the NetScaler vulnerabilities? On September 25, 2026, reports surfaced through a reddit post on r/Citrix regarding advice to shut down "Netscalers." This included a report from a user that said this information came from the "Dutch national cyber security center" and further details included a note about two zero-day vulnerabilities. On S

## Oracle September 2026 Critical Security Patch Update addresses 672 CVEs

DevFeed: [Oracle September 2026 Critical Security Patch Update addresses 672 CVEs](<https://devfeed.tech/articles/oracle-september-2026-critical-security-patch-update-addresses-672-cves-26926.md>)

Original publisher: [Read original article](<https://www.tenable.com/blog/oracle-september-2026-critical-security-patch-update-addresses-672-cves>)

Author: Research Special Operations

Published: 2026-09-15T21:00:28Z

Content type: article

Language: en

Sources: [Tenable](<https://devfeed.tech/sources/tenable-blog.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [Network](<https://devfeed.tech/topics/network.md>)

Tags: [cves](<https://devfeed.tech/tags/cves.md>), [network](<https://devfeed.tech/tags/network.md>), [security](<https://devfeed.tech/tags/security.md>), [september-2026](<https://devfeed.tech/tags/september-2026.md>), [update](<https://devfeed.tech/tags/update.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

Oracle's September 2026 Critical Security Patch Update fixes 672 unique CVEs through 673 security updates across 17 Oracle product families. It includes 104 critical patches, with Oracle E-Business Suite receiving the most patches.

### Source excerpt

Oracle addresses 672 CVEs in its September 2026 Critical Security Patch Update with 673 patches, including 104 critical updates. Key Takeaways The September 2026 Critical Security Patch Update (CSPU) contains fixes for 672 unique CVEs in 673 security updates 104 issues (15.5% of all patches) were assigned a critical severity rating Oracle E-Business Suite received the highest number of patches at 159, accounting for 23.6% of all patches Background On September 15, Oracle released its Critical Security Patch Update (CSPU) for September 2026. Beginning in May 2026, Oracle introduced CSPUs as a monthly release cycle that sits between the larger quarterly Critical Patch Updates (CPUs), addressing a focused set of high-severity issues on a faster cadence. This CSPU contains fixes for 672 unique CVEs in 673 security updates across 17 Oracle product families. Out of the 673 security updates published, 15.5% of patches were assigned a critical severity. High severity patches accounted for the bulk of security patches at 74.7%, followed by critical severity patches at 15.5%. This month's update includes 104 critical patches across 104 CVEs. SeverityIssues PatchedCVEsCritical104104High503503Medium5958Low77Total673672 Analysis This month's update saw the Oracle E-Business Suite product family contain the highest number of patches at 159, accounting for 23.6% of the total patches, followed by Oracle Fusion Middleware at 153 patches, which accounted for 22.7% of the total patches. A full breakdown of the patches for this CSPU can be seen in the following table, which also includes a count of vulnerabilities that can be exploited over a network without authentication. Oracle Product FamilyNumber of PatchesRemote Exploit without AuthOracle E-Business Suite15919Oracle Fusion Middleware15378Oracle Hyperion10250Oracle Siebel CRM6326Oracle Analytics508Oracle Communications3123Oracle Commerce2716Oracle Supply Chain195Oracle Virtualization191Oracle PeopleSoft164Oracle Database Server115

[Next page](<https://devfeed.tech/sources/tenable-blog.md?cursor=WyIyMDI2LTA5LTE1VDIxOjAwOjI4KzAwOjAwIiwgImI1YjU3MTViLTZjZTktNDE3Ni04MWE4LTViZDUyNTc3MDJlYyJd>)