← All articles

Relational database fixes code-execution flaw before version 18.7

Relational database fixes code-execution flaw before version 18.7

Administrators of the open-source relational database should install the latest security updates after the project fixed 52 flaws, including CVE-2026-6460, a high-severity vulnerability that can let a database user run code on the server. The updates released yesterday cover versions 18.7, 17.12, 16.16, 15.20 and 14.25. Fully addressing this flaw also requires rebuilding every C-language extension installed on the server.

CVE-2026-6460 is a type confusion flaw, meaning the server can mistake stored data for a different kind of data. It has a CVSS score of 8.8, a rating used to describe the severity of a security flaw. An attacker who succeeds can run commands with the permissions of the operating-system account that runs the database server. Versions before 18.7, 17.12, 16.16, 15.20 and 14.25 are affected.

The database project’s Global Development Group has not reported attacks exploiting the flaw, and the Cybersecurity and Infrastructure Security Agency, or CISA, records exploitation as none. The security advisory describes the attacker as someone who can create objects. Red Hat says the attacker needs a database login with permission to create or modify objects. The available assessments do not establish whether an account with only default privileges can move beyond causing a crash to run code.

The flaw concerns composite types, which combine named fields and assign each field its own data type. A field’s type could be changed while older values were still being held elsewhere in the server. The database server could then interpret an old value using the new type. The fix adds version checks so the database can identify values that no longer match their type.

Security researcher Mehmet Ince published a technical writeup this week describing a working exploit against version 18.6. His method prepares a query that retains a value, changes the type of one of its fields, and then runs the query. The writeup includes database commands that crash an unpatched server and a second stage that leaks memory addresses, but it does not include the commands for the final command-execution stage. Ince wrote that he could trigger the crash as a lowest-privileged login role.

Ince traced the underlying issue to a database change made on May 5, 2004, which introduced the ability to change a column’s type. His code-execution technique depends on another change made on May 14, 2015. In August, he privately shared proofs of concept with security teams at AWS for Aurora and RDS, Microsoft for Azure’s managed database service, Google for AlloyDB, Supabase, Databricks and Ubicloud. The writeup does not state the current patch status of each managed service.

The release fixes 51 other flaws as well. The project rates 32 of the 52 vulnerabilities at 8.8, the highest score in this release. Based on the project’s vulnerability index, only one server flaw requires neither a login nor user action. CVE-2026-116322 lets an unauthenticated client force version 18 servers to restart.

Several additional fixes affect client tools, which are programs used to administer or move database data. A specially crafted archive can make a restore utility run code with the permissions of the person running it. A compromised source server can make a command-line client run code through the restore script contained in a database dump archive. Administrators should therefore update client tools, including database dump, restore, reindexing and vacuum utilities, on every machine where they are used.

Administrators should update each server to the fixed release matching its major version, then rebuild or update every C-language extension. Older extensions may still load, but the database RPM package maintainers warn that they may not be protected against the vulnerabilities fixed in this release, and some may require source-code changes. Extensions rebuilt for the new releases may fail to load on older database versions, while extension packages in the project’s RPM repositories now require the corresponding new minor release.

If the database server runs outside its package’s own service unit, such as under Patroni, it should be restarted immediately after updating, according to an RPM package maintainer. Administrators should not disable the new composite-type mismatch setting, because the project warns that doing so creates security risks. The advisory and release notes provide no workaround for servers that cannot yet be updated.

Version 14 is now end-of-life, and version 14.25 is its final release. Older major versions are also affected but received no update. After patching, administrators should follow the reindexing steps in the release announcement. Organisations using incremental backups should take a new full backup and use it as the base for later incremental backups. For teams managing databases and infrastructure, AEU-I provides security-first IT, infrastructure and consulting that can support broader security planning around systems such as these.

Also available in: DeutschItalianoShqip