CVE-2026-116322: PostgreSQL · Improper Locking
Affects PostgreSQLSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 18.7 when convenient.
Data as of 12 Nov 2026, 14:48 UTC
Thin evidence
One scorer or none| CNA (PostgreSQL) | CVSS 3.1 | 5.3 |
|---|
- Patch
- Available – fixed in 18.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade PostgreSQL to 18.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PostgreSQL | Affected
| Fixed in
|
AI-suggested
A fix is available in PostgreSQL version 18.7. Users should upgrade to version 18.7 or later to remediate this vulnerability.
Description
CVE-2026-116322 is a vulnerability in PostgreSQL versions 18.0 up to but not including 18.7. It involves improper locking during startup processing, which allows an unauthenticated network client to cause a server restart by triggering authentication_timeout while holding a spinlock during cancel handling.