CVE-2026-116322
Description
A flaw was found in PostgreSQL. An unauthenticated remote attacker can cause a Denial of Service (DoS) by triggering an unexpected server restart. This issue occurs due to improper locking during startup processing when an authentication timeout occurs while a lock is held during cancel handling.
Statement
This vulnerability is rated as Moderate because an unauthenticated remote attacker can trigger an unexpected database service restart, resulting in a temporary denial of service without compromising data integrity or confidentiality. Successful exploitation requires specific timing to force a timeout during early connection processing, limiting the blast radius solely to service availability. In standard Red Hat enterprise environments, database instances are typically isolated from direct exposure to untrusted public networks, further reducing operational risk.
Mitigation
Restrict network exposure by limiting access to the PostgreSQL service to trusted hosts and subnets only, or configure the daemon to listen solely on localhost if remote connections are not required.
1. Restrict inbound network traffic using firewalld:
firewall-cmd --permanent --zone=public --remove-service=postgresql
firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_IP_OR_CIDR>
firewall-cmd --reload
2. Alternatively, configure PostgreSQL to listen only on localhost in postgresql.conf:
listen_addresses = 'localhost'Apply the configuration changes by restarting the service:
systemctl restart postgresql
Warning: Restarting or reloading the PostgreSQL service will disrupt active client connections. Restricting firewall rules or listening interfaces will prevent connections from non-allowlisted network clients, potentially impacting dependent applications if trusted endpoints are not configured correctly.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.3 | N/A | 5.3 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | Low | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Understanding the Weakness (CWE)
Integrity,Availability
Technical Impact: Modify Application Data; DoS: Instability; DoS: Crash, Exit, or Restart
When a resource is not properly locked, an attacker could modify the resource while it is being operated on by the product. This might violate the product's assumption that the resource will not change, potentially leading to unexpected behaviors.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
