Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore
Security NewsNews Explainer

Database Engine RCE Chains: Patch and Privilege Checks

Database engine RCE patch checks compare PostgreSQL, MySQL, Oracle and ClickHouse versions, privilege conditions, and post-update verification.

By
Brandefense Research Team
Reviewed by
Brandefense Analyst Team
Published
19 November 2026
Reading time
6 min read
Four abstract database server columns beside a patch verification grid

Database engine RCE patch checks now require more than a review of application table grants. Depthfirst published research on November 18 showing how restricted SQL sessions can reach native engine flaws in PostgreSQL and MySQL. Its report also describes an Oracle two-flaw chain and a reproduced ClickHouse issue. The decisions below pair that research with the available vendor patch tables.

Database Engine RCE Patch Checks by Product

Read each row as a separate exposure test, not as a shared patch level. The vendor advisories establish PostgreSQL, MySQL, and Oracle version boundaries. The vulnerability intelligence platform can help organize affected asset review; use vendor records for patch decisions. Depthfirst supplies the tested ClickHouse build and privilege condition; the pack has no ClickHouse vendor patch table.

EngineExposurePatch
Oracle AI DatabaseAffectedCVE-2026-114819 on listed branchesFixedNovember 2026 CSPU
PostgreSQLAffectedbefore branch fixesFixed18.7, 17.12, 16.16, 15.20, 14.25
MySQL Server and ClusterAffected26.7.0 to 26.7.1Unknownfixed build absent from CVE row
ClickHouseAffectedresearch tested 26.7.5.10Unknownvendor boundary not in source pack
  • Affected
  • Fixed
  • Unknown

The matrix describes the four research paths, not every flaw in those products’ security releases. For MySQL and Oracle, compare the exact installed branch with the linked vendor row. For ClickHouse, do not infer that any particular later build is fixed from a single tested image.

Where Do the Privilege Boundaries Differ?

PostgreSQL’s CVE-2026-116331 advisory describes type confusion in a min/max aggregate optimization. The planner can treat an aggregate’s input and result as the same type even when its final function changes that type. The PostgreSQL project says an object creator can then execute code as the operating system account running the database.

PostgreSQL labels the score 8.8 under CVSS 3.0; NVD labels the same score under CVSS 3.1. Neither supplied record gives a CVSS 4.0 score.

Depthfirst says a default login role can inherit TEMPORARY access and create the objects needed within its session’s temporary schema. That distinction matters: a role can lack rights on application tables yet still reach the vulnerable planner path. Review which accounts can connect, create temporary objects, and reach affected PostgreSQL instances. That is our exposure check based on the vendor description and research, not a claim that every restricted role is exploitable.

For MySQL, Depthfirst describes CVE-2026-101786 as an out-of-bounds write in a windowed bitwise aggregate. Its tested account held CREATE TEMPORARY TABLES on all databases but no SELECT access to existing application tables. The MySQL October advisory labels the flaw Server: Optimizer, rates it 7.2, and lists high privileges as a prerequisite. The research’s narrower test account and the advisory’s rating use different descriptions; verify the actual grants in your environment.

Oracle’s November 2026 security update lists CVE-2026-114819 in Oracle Text. Its risk matrix gives a 9.9 score, names Create Session as the required privilege, and lists Oracle Net as the protocol. Depthfirst says that flaw can be chained with CVE-2026-91609 in a GraphQL interface to reach code execution from an exposed HTTP endpoint without a database login. Treat the unauthenticated route as the researcher’s chained scenario, not Oracle’s stated precondition for CVE-2026-114819 alone.

Unlike the earlier ClickHouse vulnerability, this example reports an unchecked RowBinary length calculation and a proof of concept on 26.7.5.10. Its tested user held only CREATE TEMPORARY TABLE ON all databases. Check whether a comparable role can access the service and whether the deployment uses the research-tested build. A vendor affected-range and fixed-build claim needs a separate ClickHouse advisory.

Which Builds Need a Patch Decision?

PostgreSQL says versions before 18.7, 17.12, 16.16, 15.20, and 14.25 are affected in their respective branches. It published those fixes on November 12, 2026. Inventory the running server version, select the matching branch fix, and confirm the running version after restart. A package name or change ticket alone does not prove that the database process loaded the update.

MySQL’s October 20 advisory lists 26.7.0 through 26.7.1 for both MySQL Server and MySQL Cluster under CVE-2026-101786. The table gives the affected set rather than a specific fixed build in that row. Obtain the vendor’s applicable update, then verify the running version against its released patch guidance. Include Cluster deployments when the same affected range appears in inventory.

For Oracle, the November matrix lists CVE-2026-114819 on Database Server 19.3 to 19.32, 21.3 to 21.24, and 23.4.0 to 23.26.3. Apply the November security update for the installed supported branch. If the GraphQL interface is exposed, also check the status of the separate October CVE-2026-91609 correction. The November row alone does not prove that both links in the researcher’s chain have been closed.

Oracle says its security patches target releases in Premier or Extended Support. It warns that unsupported earlier releases may also be affected and recommends moving to supported versions. For ClickHouse, ask the vendor or deployment owner for an affected-range and fixed-build record before marking the tested path closed. These product-specific checks are safer than treating a shared change window as proof that every engine is remediated.

How Should Teams Prioritize and Verify?

Start with the combination of an affected build and a reachable role or interface. For PostgreSQL, inspect TEMPORARY grants and object creation rights for low-trust accounts. For MySQL and ClickHouse, inspect temporary-table privileges alongside version records. For Oracle, review both database session access and any exposed GraphQL route described by the research.

These are our defensive checks drawn from the documented prerequisites. Keep the pre-update version and access result together for later verification.

Brandefense Blackhole counted one dark-chat post mentioning CVE-2026-116331 from August 21 through November 19, 2026. A GitHub name search on November 19 found one public repository naming that CVE. These are separate units and may overlap in attention; neither count establishes an incident or exploitation. The public repository listing is a research signal, not a deployment exposure measurement.

The CISA KEV snapshot dated November 18 did not list CVE-2026-116331. A catalog absence is a dated prioritization fact, not evidence that an unpatched server is safe. Vendor records remain the source for patch decisions.

Engine patch and privilege verification
  • InventoryRecord engine, edition, running branch, owner, and relevant network entry points.
  • CompareMatch each installed build to its own vendor affected range or research-tested build.
  • Inspect accessReview temporary-object grants, database sessions, and exposed interfaces.
  • PatchApply the matching vendor update; request a ClickHouse fix record before closing that row.
  • VerifyConfirm the running build and recheck the role or interface that made the path reachable.

Keep an evidence record for each instance: its pre-update version, the selected advisory, the actual running build, and the access review. The patch management process helps preserve that before and after trail. Our PostgreSQL November release coverage gives context for the broader update, while this comparison focuses on low-privilege engine paths.

Frequently Asked Questions

Does a read-restricted database role remove the RCE risk?

Not by itself. Depthfirst showed paths using temporary-object privileges in PostgreSQL, MySQL, and ClickHouse. Check each account's effective grants and the installed build.

Which PostgreSQL release fixes CVE-2026-116331?

PostgreSQL names 18.7, 17.12, 16.16, 15.20, and 14.25 as fixed releases for their respective branches.

Is Oracle CVE-2026-114819 unauthenticated by itself?

Oracle lists Create Session for that CVE. Depthfirst describes an unauthenticated HTTP path when it is chained with the separate GraphQL flaw CVE-2026-91609.

Which ClickHouse build is fixed?

The available research reports a test on 26.7.5.10. It does not provide a vendor fixed-build boundary, so confirm that boundary with ClickHouse before closing the item.

Sources

  1. Depthfirst, Narrow Grants, Wide Engines
  2. PostgreSQL CVE-2026-116331 advisory
  3. NVD CVE-2026-116331 record
  4. MySQL Community Edition Security Advisory, October 2026
  5. Oracle November 2026 Critical Security Patch Update
  6. CISA Known Exploited Vulnerabilities catalog
Share this articleLinkedInXEmail
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →