JLSEC-2026-26
Record from OSV · Published April 3, 2026
A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If a client application that creates additional database connections only reuses the basic connection parameters while dropping security-relevant parameters, an opportunity for a man-in-the-middle attack, or the ability to observe clear-text transmissions, could exist. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| LibPQ_jll | juliahub.com | 14.1.0+0 |
| LibPQ_jll | pkg.julialang.org | 14.1.0+0 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Julia | LibPQ_jll | 0 |
| Julia | LibPQ_jll | 0 |
Timeline
- Apr 3, 2026 CVE Published
- Jul 18, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln JLSEC-2026-26
vulnetix vdb fixes JLSEC-2026-26Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/JLSEC-2026-26/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart