| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00+ |
Summary
A vulnerability was found in PostgreSQL up to 14.24/15.19/16.15/17.11/18.6. It has been classified as problematic. This impacts an unknown function. This manipulation causes null termination. This vulnerability is tracked as CVE-2026-116321. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic was found in PostgreSQL up to 14.24/15.19/16.15/17.11/18.6. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a null termination vulnerability. The CWE definition for the vulnerability is CWE-170. The product does not terminate or incorrectly terminates a string or array with a null character or equivalent terminator. As an impact it is known to affect confidentiality. The summary by CVE is:
Improper null termination in PostgreSQL array element assignment allows a database user to disclose server memory, via changing the final byte of a fixed-length name value to a nonzero byte and passing it to code that treats the value as a C string. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
The advisory is shared at postgresql.org. This vulnerability is known as CVE-2026-116321 since 10/26/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version 14.25, 15.20, 16.16, 17.12 or 18.7 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 14.0
- 14.1
- 14.2
- 14.3
- 14.4
- 14.5
- 14.6
- 14.7
- 14.8
- 14.9
- 14.10
- 14.11
- 14.12
- 14.13
- 14.14
- 14.15
- 14.16
- 14.17
- 14.18
- 14.19
- 14.20
- 14.21
- 14.22
- 14.23
- 14.24
- 15.0
- 15.1
- 15.2
- 15.3
- 15.4
- 15.5
- 15.6
- 15.7
- 15.8
- 15.9
- 15.10
- 15.11
- 15.12
- 15.13
- 15.14
- 15.15
- 15.16
- 15.17
- 15.18
- 15.19
- 16.0
- 16.1
- 16.2
- 16.3
- 16.4
- 16.5
- 16.6
- 16.7
- 16.8
- 16.9
- 16.10
- 16.11
- 16.12
- 16.13
- 16.14
- 16.15
- 17.0
- 17.1
- 17.2
- 17.3
- 17.4
- 17.5
- 17.6
- 17.7
- 17.8
- 17.9
- 17.10
- 17.11
- 18.0
- 18.1
- 18.2
- 18.3
- 18.4
- 18.5
- 18.6
License
Website
- Product: https://www.postgresql.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.3
CNA Vector (PostgreSQL): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Null terminationCWE: CWE-170 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: PostgreSQL 14.25/15.20/16.16/17.12/18.7
Timeline
10/26/2026 CVE reserved11/12/2026 Advisory disclosed
11/12/2026 VulDB entry created
11/12/2026 VulDB entry last update
Sources
Product: postgresql.orgAdvisory: postgresql.org
Status: Confirmed
CNA: PostgreSQL
CVE: CVE-2026-116321 (🔒)
GCVE (CVE): GCVE-0-2026-116321
GCVE (VulDB): GCVE-100-436357
Entry
Created: 11/12/2026 15:37Changes: 11/12/2026 15:37 (62)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.