SAASMENT

News

Low-privilege database logins can run code on the server.

Proofs of concept show that ordinary SQL can reach memory bugs in PostgreSQL, MySQL, and ClickHouse, and that a separate Oracle chain needs no login. None of the chains has been seen in a real attack.

Illustration of database cylinders, one cracked open and one with an open doorway

Impact

What was impacted
Memory-corruption bugs in database engine code, reached through SQL rather than through permission to read application tables. PostgreSQL CVE-2026-116331, in versions before 18.7, 17.12, 16.16, 15.20, and 14.25, fixed on 12 November. MySQL Server and Cluster CVE-2026-101786, versions 26.7.0 through 26.7.1, fixed on 20 October. Oracle Text CVE-2026-114819, rated 9.9, in 19.3–19.32, 21.3–21.24, and 23.4.0–23.26.3, fixed on 17 November, chained with Oracle REST Data Services GraphQL CVE-2026-91609, versions 24.2.0 through 26.2.1, fixed on 20 October. ClickHouse: an integer-overflow write while reading a binary row format, tested on 26.7.5.10, with no CVE and no confirmed fixed version.
Who was impacted
Operators of those databases. On PostgreSQL, the default TEMPORARY privilege is enough for an account to create the objects the researcher used. On MySQL and ClickHouse, the right to create temporary tables is the access described. Oracle’s MySQL advisory rates CVE-2026-101786 as needing high privileges; the researcher reported code execution on the 26.7.0 image with an account that could only create temporary tables and could not read existing ones. Oracle Database is the chain the researcher says needs no account, when the Text bug and the ORDS GraphQL flaw are used together against an exposed web endpoint. On their own, Oracle rates neither of those two as exploitable without a login.
What you need to do
Install the fixed PostgreSQL, MySQL, Oracle Database, and Oracle REST Data Services builds named above. Remove the TEMPORARY privilege and unused temporary-table rights from accounts that do not need them. That review does not close the Oracle path, which starts without an account, so install both Oracle fixes and check whether the web endpoint is exposed. For ClickHouse, ask the vendor which build is fixed. Do not guess a version. The full attack chains were not reproduced independently, and the report says none has been used in an attack.

Zheng Yu of Depthfirst published proofs of concept showing that a database login which cannot read application tables can still run code on the database server, by hitting memory-corruption bugs in the C and C++ that plans and executes SQL. The targets are PostgreSQL, MySQL, and ClickHouse, plus a separate Oracle chain that the researcher says needs no login. The report says none of these has been seen in a real attack. Four of the flaws have vendor CVEs and fixes. The full attack chains were not reproduced independently.

In PostgreSQL, CVE-2026-116331 lets an account that can create database objects run code as the operating-system user that runs the database. The researcher’s analysis describes a normal login role building objects in its own temporary schema, without reading application data, then using a type-confusion bug to take control of the server. It was fixed on 12 November. The affected ranges named in the report are versions before 18.7, 17.12, 16.16, 15.20, and 14.25. PostgreSQL’s default TEMPORARY privilege is enough to create those objects.

MySQL’s query-optimizer flaw is CVE-2026-101786, in Server and Cluster 26.7.0 through 26.7.1, fixed on 20 October. Oracle’s October advisory rates it as needing high privileges. The researcher reported code execution on the 26.7.0 image using an account that could only create temporary tables and could not read existing ones, which is narrower than that rating. ClickHouse is an integer-overflow write while reading a binary row format. The researcher says a user who sets format_binary_max_string_size to zero can reach it, and reported a shell on 26.7.5.10. That issue has no CVE and no confirmed fixed version.

Oracle Database is the chain the researcher says needs no account. A bug in Oracle Text, CVE-2026-114819, rated 9.9, and a flaw in the GraphQL interface of Oracle REST Data Services, CVE-2026-91609, used together against an exposed web endpoint, reach engine code and run commands before any login. Oracle patched the Text bug on 17 November for 19.3–19.32, 21.3–21.24, and 23.4.0–23.26.3, and the GraphQL flaw on 20 October for ORDS 24.2.0 through 26.2.1. On their own, the company rates neither as exploitable without a login.

Install those fixed builds. Also review what accounts can create, not only what they can read, and remove the TEMPORARY privilege and broad temporary-table rights from accounts that do not need them. That review does not close the Oracle path, which starts with no account. For ClickHouse, confirm a fixed build with the vendor before you treat a version as safe.

For your AI agent

Agent instructions — copy paste to Claude

You are helping me respond to memory-corruption bugs in database engines that a researcher showed can be reached through SQL, including by accounts that cannot read application tables. The work is by Zheng Yu of Depthfirst. Proofs of concept were published for PostgreSQL, MySQL, and ClickHouse, plus a separate Oracle chain the researcher says needs no login. The report says none has been seen in a real attack. The full attack chains were not reproduced independently. Do not download or run those proofs of concept, and do not write a new one.

Fixed or unfixed items from the report:
- PostgreSQL CVE-2026-116331. An account that can create database objects can run code as the operating-system user that runs the database. The analysis describes a login role using its own temporary schema and a type-confusion bug, without reading application data. PostgreSQL's default TEMPORARY privilege is enough to create those objects. Affected: versions before 18.7, 17.12, 16.16, 15.20, and 14.25. Fixed 12 November.
- MySQL Server and Cluster CVE-2026-101786, a query-optimizer flaw in 26.7.0 through 26.7.1. Fixed 20 October. Oracle's October advisory rates it as needing high privileges. The researcher reported code execution on the 26.7.0 image with an account that could only create temporary tables and could not read existing ones.
- Oracle Text CVE-2026-114819, rated 9.9, in 19.3-19.32, 21.3-21.24, and 23.4.0-23.26.3. Fixed 17 November. Oracle REST Data Services GraphQL CVE-2026-91609, versions 24.2.0 through 26.2.1. Fixed 20 October. The researcher says the two, used together against an exposed web endpoint, run commands before any login. On their own, Oracle rates neither as exploitable without a login.
- ClickHouse: integer-overflow write while reading a binary row format. The researcher says a user who sets format_binary_max_string_size to zero can reach it, and reported a shell on 26.7.5.10. No CVE and no confirmed fixed version. Do not invent one.

Context:
- What was impacted: the database server process, not only the tables an account can read.
- Who should care: operators of the versions above, especially where TEMPORARY or temporary-table rights are broad, and where an Oracle REST Data Services web endpoint is exposed.
- What to do: install the named fixes, tighten create privileges that are not needed, and ask the ClickHouse vendor for a fixed build. Removing TEMPORARY rights does not close the Oracle path.

Do this in order. Ask before changing grants, restarting databases, or installing patches. Prefer read-only inventory first. Do not write or run an exploit, a proof of concept, or SQL meant to trigger these bugs.

1. Inventory
   - Record PostgreSQL, MySQL Server or Cluster, Oracle Database, Oracle REST Data Services, and ClickHouse versions. Compare them only to the ranges above. If a version is missing from this list, say it was not named, and do not mark it safe.
   - For PostgreSQL, list roles that still have TEMPORARY, which is often the default. For MySQL and ClickHouse, list accounts that can create temporary tables.
   - For ClickHouse, record whether untrusted users can set format_binary_max_string_size, including to zero.
   - For Oracle, record whether an ORDS web endpoint is reachable beyond the people who should use it, and whether the Text and ORDS builds above are still in the affected ranges.
2. Contain
   - Propose removing TEMPORARY and unused temporary-table rights from accounts that do not need them. Say clearly that this does not close the Oracle no-login path.
   - Propose keeping untrusted ClickHouse users from setting format_binary_max_string_size to zero until a vendor fix is confirmed.
   - Ask before applying any grant or setting change.
3. Remediate
   - Plan PostgreSQL updates to 18.7, 17.12, 16.16, 15.20, or 14.25, or a newer build on those lines. The report dates that fix to 12 November.
   - MySQL Server and Cluster 26.7.0 through 26.7.1 are the affected range, so 26.7.1 is still inside it. The report dates the fix to 20 October and does not name the fixed build. If a vendor advisory in front of you names that build, use it. If it does not, say the fixed version number was not in the report.
   - Plan Oracle Text updates from the 17 November fix for the ranges above, and ORDS updates from the 20 October fix for 24.2.0 through 26.2.1. The report does not name fixed Oracle build numbers beyond those dates and ranges.
   - For ClickHouse, stop and ask the vendor which version is fixed. Do not pick one.
   - Ask before installing or restarting.
4. Verify
   - Confirm the running server versions match the builds you intended, and re-check the grants you changed.
5. Report back
   - Versions found, which accounts can create temporary objects, whether the Oracle web endpoint is exposed, what was patched or revoked, and anything still on an unnamed or unfixed build.

Do not invent CVEs, package versions, or exploit steps. If a check needs access I have not given you, say what you need and stop.

← All news

Try the platform.

Open the demo workspace with mock data. No login. Register from the banner when you want early access. No security team. No call.

Try the platform