Loading vulnerability…
PostGREShell is a missing-authorization vulnerability in PostgreSQL logical decoding. A non-superuser role holding the REPLICATION attribute can provide an arbitrary logical-decoding output-plugin library name when creating a replication slot. Vulnerable releases pass that value to the operating-system dynamic library loader without enforcing the normal non-superuser plugin-location restriction, permitting filesystem paths and traversal sequences. A selected shared library that is accessible to the PostgreSQL service account is loaded into a PostgreSQL backend process, executing its code under that operating-system account. The issue affects PostgreSQL releases before 18.6, 17.11, 16.15, 15.19, and 14.24 in the respective supported branches.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This eight-file repository is an operational proof of concept for CVE-2026-6471, a post-authentication PostgreSQL privilege escalation through logical decoding output-plugin selection. The primary entry point is an Exploitmatic declarative solution stored in cve-2026-6471-postgres-logical-decoding-dlopen.txt. It checks that repro_rep is a non-superuser REPLICATION role, verifies normal pgoutput slot creation, base64-decodes pwn.so to /tmp/pwn.so in a Docker container, and requests that PostgreSQL create a logical replication slot using that library path as the plugin. On the stated vulnerable PostgreSQL 16.14 target, the server loads the library in a backend process as the postgres OS account. The C payload's constructor writes a local marker and launches psql to create a persistent database superuser backdoor role. The final solution step authenticates as that role to verify takeover. The lab directory contains a provisioning shell script plus nearly identical Dockerfiles for PostgreSQL 16.14 and patched 16.15, both configured with wal_level=logical. The documented fix is an output_plugin_libraries allowlist, which rejects arbitrary plugin paths before dlopen. This is not unauthenticated remote exploitation: it needs a replication-capable account, logical decoding enabled, attacker-controlled library placement, and suitable local PostgreSQL peer/trust authentication for the postgres OS account.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
62 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A PostgreSQL arbitrary-code-execution vulnerability involving a logical decoding plugin.
A PostgreSQL logical-decoding output-plugin library-path validation flaw. An authenticated non-superuser account with the REPLICATION attribute can specify an attacker-controlled library path, causing PostgreSQL to load it and execute code with the privileges of the PostgreSQL server process. The flaw dates to PostgreSQL 9.4 (2014).
A PostgreSQL logical-decoding vulnerability, present since PostgreSQL 9.4, that lets a non-superuser account with the REPLICATION attribute supply an insufficiently restricted output-plugin library path. PostgreSQL can then load an attacker-controlled shared library, resulting in arbitrary code execution under the PostgreSQL server process account.
A PostgreSQL logical-decoding output-plugin loading restriction bypass that can allow a REPLICATION-privileged user to load attacker-controlled DLLs or shared libraries, execute arbitrary OS code, elevate to database superuser, and establish persistence or pivot to host compromise. The issue affects PostgreSQL logical decoding introduced in version 9.4.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.