Skip to content
Fencer Intel
medium 5.3

CVE-2026-116322 json

PostgreSQL pre-authentication cancel request can leak a spinlock

published 2d ago modified 2d ago also EUVD-2026-124502

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

Improper locking in PostgreSQL startup processing allows an unauthenticated network client to trigger a server restart, via arranging for authentication_timeout to arrive while it holds a spinlock during cancel handling. Within major version 18, minor versions before PostgreSQL 18.7 are affected. Versions before PostgreSQL 18 are unaffected.

Patch / fix

  • n/a PostgreSQL 18.7
  • postgresql15 Alpine 3.22, Alpine 3.21 15.20-r0
  • postgresql16 Alpine 3.24, Alpine 3.23, Alpine 3.22 +1 more 16.16-r0
  • postgresql17 Alpine 3.24, Alpine 3.23, Alpine 3.22 +1 more 17.12-r0
  • postgresql18 Alpine 3.24, Alpine 3.23 18.7-r0

alpine advisories ALPINE-CVE-2026-116322

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2026-116322 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-116322 updated cvss 5.3

postgresql: postgresql: Denial of Service via improper locking during startup processing

  • Red Hat Enterprise Linux 9 postgresql, postgresql-test, postgresql-pltcl, postgresql-plperl, postgresql-server, postgresql-contrib, +5 more Red Hat Enterprise Linux 10 postgresql18, rhel10/postgresql-18
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Hardened Images postgresql18
    affected: workaround, no fix available
  • Red Hat Advanced Cluster Security 4 advanced-cluster-security/rhacs-central-db-rhel8, advanced-cluster-security/rhacs-central-db-rhel9, advanced-cluster-security/rhacs-scanner-db-rhel8, advanced-cluster-security/rhacs-scanner-db-rhel9, advanced-cluster-security/rhacs-scanner-v4-db-rhel8, advanced-cluster-security/rhacs-scanner-v4-db-rhel9, +2 more Red Hat Advanced Cluster Security 5 advanced-cluster-security/rhacs-central-db-rhel9, advanced-cluster-security/rhacs-scanner-v4-db-rhel9 Red Hat Enterprise Linux 6 postgresql, postgresql-libs, postgresql-test, postgresql-pltcl, postgresql-plperl, postgresql-server, +2 more Red Hat Enterprise Linux 7 postgresql, postgresql-libs, postgresql-test, postgresql-pltcl, postgresql-plperl, postgresql-server, +3 more Red Hat Enterprise Linux 8 pgaudit, pg_repack, postgresql, postgresql-test, postgresql-pltcl, postgresql-plperl, +11 more Red Hat Enterprise Linux 9 postgresql, postgresql-test, postgresql-pltcl, postgresql-plperl, postgresql-server, postgresql-contrib, +7 more
    +3 more products
    Red Hat Enterprise Linux 10 postgresql16, postgresql19, rhel10/postgresql-16 Red Hat Hardened Images hi/postgresql Red Hat Self-service automation portal 2 ansible-automation-platform/bootc-automation-portal-rhel9
    under investigation
  • Red Hat Hardened Images libpq 18.7-0.1.hum1, postgresql17 17.11-1.2.hum1, postgresql17-test 17.11-1.2.hum1, postgresql17-pltcl 17.11-1.2.hum1, postgresql17-plperl 17.11-1.2.hum1, postgresql17-server 17.11-1.2.hum1, +5 more
    fixed: vendor fix RHSA-2026:99821

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2d ago

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-14).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected products

  • n/a PostgreSQL

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.