Executive Summary
In November 2026, security researcher Zheng Yu of Depthfirst published proof-of-concept exploits demonstrating remote code execution (RCE) against PostgreSQL, MySQL, ClickHouse, and Oracle Database, exposing a critical architectural gap: low-privilege database accounts with no access to application data can still trigger memory-corruption bugs in the underlying C/C++ engine code through ordinary SQL operations. Four CVEs were assigned and patched across PostgreSQL (CVE-2026-116331), MySQL (CVE-2026-101786), Oracle Text (CVE-2026-114819, CVSS 9.9), and Oracle REST Data Services (CVE-2026-91609). The Oracle chain requires no login at all, exploiting exposed web endpoints pre-authentication. ClickHouse remains without a confirmed fix.
This research reframes database privilege models as insufficient security boundaries: SQL-level access controls do not constrain memory-unsafe engine execution paths. With four major database platforms affected simultaneously and one unauthenticated Oracle chain active, organizations relying solely on database-level permissions face systemic RCE exposure across hybrid and multi-cloud data tiers.
Why This Matters Now
Database servers sit at the core of every regulated workload—PCI, HIPAA, SOX. These exploits prove that least-privilege SQL grants alone cannot prevent RCE when the engine itself is reachable via ordinary queries or unauthenticated web endpoints. With patches still incomplete for ClickHouse and the Oracle unauthenticated path only recently closed, organizations must urgently audit temporary-table privileges and enforce network-layer controls around database tiers to contain lateral movement and exfiltration risk.
Attack Path Analysis
An attacker targeting exposed database infrastructure exploits memory-corruption vulnerabilities in PostgreSQL, MySQL, ClickHouse, or Oracle REST Data Services — in Oracle's case requiring no credentials — to achieve remote code execution on the database server OS. From there, the attacker escalates to OS-level privileges, moves laterally across database tiers, establishes command-and-control via outbound channels, exfiltrates sensitive data, and ultimately causes operational or data integrity impact.
Kill Chain Progression
This analysis maps confirmed threat intelligence to the full cloud kill chain to show where defensive gaps would emerge as an attack progresses.
Initial Compromise
Description
For PostgreSQL, MySQL, and ClickHouse, an attacker obtains a low-privilege database account (e.g., one with only TEMPORARY table rights) and crafts SQL input that triggers a memory-corruption bug in the database engine's C/C++ code (CVE-2026-116331, CVE-2026-101786, ClickHouse integer overflow). For Oracle, no login is required: the attacker chains CVE-2026-114819 (Oracle Text, CVSS 9.9) with CVE-2026-91609 (Oracle REST Data Services GraphQL endpoint) against an exposed web endpoint to reach engine code without authentication.
Related CVEs
CVE-2026-116331
CVSS 8.8A type-confusion memory corruption vulnerability in PostgreSQL allows a low-privilege account with TEMPORARY object creation rights to escalate to operating system-level code execution as the database server process user.
Affected Products:
PostgreSQL Global Development Group PostgreSQL – < 14.25, < 15.20, < 16.16, < 17.12, < 18.7
Exploit Status:
proof of conceptCVE-2026-101786
CVSS 7.2A memory corruption flaw in the MySQL Server and Cluster query optimizer allows an account with only temporary table creation privileges to achieve remote code execution on affected versions 26.7.0 through 26.7.1.
Affected Products:
Oracle MySQL Server – 26.7.0, 26.7.1
Oracle MySQL Cluster – 26.7.0, 26.7.1
Exploit Status:
proof of conceptCVE-2026-114819
CVSS 9.9A critical vulnerability in Oracle Text (rated 9.9) allows unauthenticated remote attackers to execute arbitrary commands on the database server by chaining it with a GraphQL flaw in Oracle REST Data Services against an exposed web endpoint.
Affected Products:
Oracle Oracle Database (Oracle Text) – 19.3 - 19.32, 21.3 - 21.24, 23.4.0 - 23.26.3
Exploit Status:
proof of conceptCVE-2026-91609
CVSS 6.5A vulnerability in the GraphQL interface of Oracle REST Data Services allows unauthenticated attackers to chain with Oracle Text flaws to reach engine-level code execution without any database login.
Affected Products:
Oracle Oracle REST Data Services – 24.2.0 - 26.2.1
Exploit Status:
proof of concept
MITRE ATT&CK® Techniques
Exploit Public-Facing Application
Exploitation for Client Execution
Command and Scripting Interpreter
Exploitation for Privilege Escalation
Valid Accounts: Local Accounts
Exploitation of Remote Services
Abuse Elevation Control Mechanism
External Remote Services
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Timely Patching of Software Vulnerabilities
Control ID: Requirement 6.3.3
NYDFS 23 NYCRR 500 – Least-Privilege Access Control for Database Accounts
Control ID: Section 500.7 — Access Privileges
DORA (Digital Operational Resilience Act) – Patch and Vulnerability Management for Critical ICT Systems
Control ID: Article 9 — ICT Security Policies and Vulnerability Management
CISA Zero Trust Maturity Model 2.0 – Granular Database Permission Enforcement and Privileged Access Controls
Control ID: Data Pillar — Data Access Management
NIS2 Directive – Proactive Vulnerability Management and Coordinated Remediation
Control ID: Article 21(2)(e) — Vulnerability Handling and Disclosure
ISO/IEC 27001:2022 – Technical Vulnerability Assessment and Remediation
Control ID: Annex A 8.8 — Management of Technical Vulnerabilities
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Financial Services
Database RCE exploits targeting PostgreSQL, MySQL, and Oracle expose financial platforms to privilege escalation and exfiltration, violating PCI 4.0 and NIST 800-53 controls governing transactional data integrity and lateral movement containment.
Health Care / Life Sciences
Low-privilege RCE chains against Oracle and PostgreSQL threaten clinical database infrastructure, undermining HIPAA 164.312 safeguards and enabling unauthorized exfiltration of protected health information without requiring elevated account credentials.
Information Technology/IT
CVE-2026-116331 and related database engine flaws directly impact IT infrastructure teams managing multicloud deployments, demanding Zero Trust segmentation and inline IPS controls to prevent unauthenticated Oracle RCE and lateral movement.
Banking/Mortgage
Oracle's pre-authentication RCE chain via exposed web endpoints threatens banking transaction databases, requiring urgent egress policy enforcement and east-west traffic controls to prevent silent data exfiltration from core lending systems.
Sources
- Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oraclehttps://thehackernews.com/2026/11/researcher-demonstrates-database-rce.htmlVerified
- PostgreSQL Security Advisory: CVE-2026-116331https://www.postgresql.org/support/security/CVE-2026-116331/Verified
- Oracle MySQL Community Security Advisory October 2026https://dev.mysql.com/community/security/advisories/2026-10-20/Verified
- Oracle Critical Patch Update November 2026https://www.oracle.com/security-alerts/cspunov2026.htmlVerified
- Oracle Critical Patch Update October 2026https://www.oracle.com/security-alerts/cpuoct2026.htmlVerified
- Narrow Grants Wide Engines - Depthfirst Security Researchhttps://depthfirst.com/research/narrow-grants-wide-enginesVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.
Aviatrix Zero Trust CNSF is directly relevant here because attackers exploited exposed database endpoints to gain OS-level footholds and move freely across internal tiers — conditions that identity-aware segmentation and controlled egress enforcement are specifically designed to constrain. By limiting reachability to database workloads and restricting outbound paths, CNSF would likely reduce the attacker's ability to pivot, beacon, and exfiltrate at scale.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Restricting which network sources could reach database service ports would likely reduce the exposed attack surface, making it harder for external actors to deliver exploit payloads directly to vulnerable database endpoints.
Control: Zero Trust Segmentation
Mitigation: Enforcing least-privilege identity-based segmentation policies around the database OS user context would likely constrain what resources and services the compromised process could reach, reducing the blast radius even after OS-level execution is achieved.
Control: East-West Traffic Security
Mitigation: Workload-to-workload segmentation enforced across internal tiers would likely constrain the attacker's ability to pivot freely from the compromised database host to adjacent services, reducing the number of reachable targets within the environment.
Control: Multicloud Visibility & Control
Mitigation: Multicloud visibility into outbound connection patterns from database workloads would likely surface anomalous egress behavior early, giving teams the context needed to constrain unauthorized C2 channels before they become persistent.
Control: Egress Security & Policy Enforcement
Mitigation: FQDN-based egress allowlists and outbound traffic policy enforcement would likely constrain the attacker's ability to transfer bulk data to unauthorized external destinations, reducing the volume and reach of data that could be exfiltrated from the compromised host.
Because lateral movement and egress were likely constrained by earlier CNSF controls, the attacker's impact would likely be scoped closer to the initially compromised database workload rather than spreading across dependent application tiers or additional cloud environments.
Impact at a Glance
Affected Business Functions
- Database-Backed Application Services
- Data Integrity and Confidentiality of Application Records
- Database Server Operating System Integrity
- API and Web Endpoint Security (Oracle REST Data Services)
Estimated downtime: 7 days
Estimated loss: N/A
Any data stored within affected PostgreSQL, MySQL, or Oracle Database instances is at risk of full exfiltration or modification. Because the exploits achieve OS-level code execution, attackers could access all application tables, credentials, cryptographic material, and configuration files residing on the database host. The Oracle chain requires no prior authentication, meaning externally exposed Oracle REST Data Services endpoints place entire database contents at risk without any attacker foothold. ClickHouse deployments running version 26.7.5.10 with user-configurable binary format options are similarly exposed to full data compromise and shell access. No confirmed exfiltration has been reported; risk is currently limited to proof-of-concept exposure.
Recommended Actions
Key Takeaways & Next Steps
- • Apply all vendor patches immediately for CVE-2026-116331 (PostgreSQL), CVE-2026-101786 (MySQL), CVE-2026-114819 and CVE-2026-91609 (Oracle), and restrict ClickHouse deployments to vendor-confirmed fixed versions; patch the Oracle GraphQL/REST endpoint exposure as the unauthenticated entry point represents the highest-priority risk.
- • Enforce Zero Trust Segmentation by auditing and revoking TEMPORARY table privileges and broad temporary-table rights from all database accounts that do not explicitly require them, applying least-privilege identity-based policies aligned with ZTMM.Network and NIST.800-53.AC-6 to constrain the SQL-to-OS attack surface.
- • Deploy East-West Traffic Security controls to enforce workload-to-workload microsegmentation between database hosts and adjacent application or infrastructure tiers, ensuring that OS-level compromise of a database server cannot be used for uninspected lateral movement to other internal services.
- • Implement Egress Security & Policy Enforcement with FQDN-based allowlists and Cloud Firewall (ACF) rules to block unauthorized outbound connections from database hosts, preventing reverse-shell C2 establishment and direct data exfiltration from compromised database OS contexts.
- • Enable Multicloud Visibility & Control and Inline IPS (Suricata) with signatures covering known database exploit traffic patterns and anomalous bulk outbound data transfer, providing detection and inline blocking capability for exploit attempts and post-compromise exfiltration across all database tiers.



