🛡️ JLSEC-2026-52 — libpq-jll
Description
Time-of-check Time-of-use (TOCTOU) race condition in pg_dump in PostgreSQL allows an object creator to execute arbitrary SQL functions as the user running pg_dump, which is often a superuser. The attack involves replacing another relation type with a view or foreign table. The attack requires waiting for pg_dump to start, but winning the race condition is trivial if the attacker retains an open transaction. Versions before PostgreSQL 16.4, 15.8, 14.13, 13.16, and 12.20 are affected.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is high, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.
Affected software
JLSEC-2026-52 is recorded against 1 package.
- libpq-jll
Timeline and source
Published on 3 April 2026 and last revised on 25 July 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
www.openwall.com (Web)
security.netapp.com (Web)
www.postgresql.org (Web)
Details
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| libpq-jll | — | — |
References
Similar Threats
- Unknown JLSEC-2026-24
- Unknown JLSEC-2026-25
- Unknown JLSEC-2026-26
- Unknown JLSEC-2026-27
- Unknown JLSEC-2026-28
More JLSEC 2026 advisories
Browse all of JLSEC 2026 in the advisory index.
Free Vulnerability Check
Is your site affected by JLSEC-2026-52?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against JLSEC-2026-52 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.