No exploitation reportedFix available

CVE-2023-5869

Q: Is CVE-2023-5869 actively exploited?

Active exploitation of CVE-2023-5869 has not been confirmed. Its EPSS score was 4.3% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

Q: What is the CVSS score for CVE-2023-5869?

CVE-2023-5869 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

No exploitation reported by the sources we read.

Published2023-12-10
Fixed in15.5 · 14.10 · 13.13 · 12.17 · 11.22
WeaknessCWE-190

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A flaw was found in PostgreSQL that allows authenticated database users to execute arbitrary code through missing overflow checks during SQL array value modification. This issue exists due to an integer overflow during array modification where a remote user can trigger the overflow by providing specially crafted data. This enables the execution of arbitrary code on the target system, allowing users to write arbitrary bytes to memory and extensively read the server's memory.

Timeline

dates in UTC

2023-12-1018:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-5869?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-5869?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

PostgreSQL

Branch	Affected	Fixed in	Source
15.x	≥ 15.0, < 15.5	15.5	NVD
14.x	≥ 14.0, < 14.10	14.10	NVD
13.x	≥ 13.0, < 13.13	13.13	NVD
12.x	≥ 12.0, < 12.17	12.17	NVD
11.x	≥ 11.0, < 11.22	11.22	NVD
16.0	= 16.0	no fix published	NVD

Redhat enterprise linux eus

Branch	Affected	Fixed in	Source
8.6	= 8.6	no fix published	NVD
8.8	= 8.8	no fix published	NVD
9.0	= 9.0	no fix published	NVD
9.2	= 9.2	no fix published	NVD

Redhat enterprise linux for ibm z systems eus

Branch	Affected	Fixed in	Source
8.6	= 8.6_s390x	no fix published	NVD
8.8	= 8.8_s390x	no fix published	NVD
9.0	= 9.0_s390x	no fix published	NVD
9.2	= 9.2_s390x	no fix published	NVD

18 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

RHSA-2023:7772 Red Hat Product Security66 products fixed
Red Hat Security Advisory: rh-postgresql13-postgresql security update
RHSA-2023:7695 Red Hat Product Security192 products fixed
Red Hat Security Advisory: postgresql:13 security update
RHSA-2023:7694 Red Hat Product Security192 products fixed
Red Hat Security Advisory: postgresql:12 security update
RHSA-2023:7666 Red Hat Product Security137 products fixed
Red Hat Security Advisory: postgresql:12 security update
RHSA-2023:7667 Red Hat Product Security132 products fixed
Red Hat Security Advisory: postgresql:12 security update
RHSA-2023:7580 Red Hat Product Security137 products fixed
Red Hat Security Advisory: postgresql:13 security update

1 more advisory

Full record on NVD

Fix

Update PostgreSQL to 15.5 · 14.10 · 13.13 · 12.17 · 11.22
Vendor fix Red Hat Product Security RHSA-2023:7772 · 66 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 If the postgresql service is running, it will be automatically restarted after installing this update.
Workaround from the vendor Red Hat Product Security RHSA-2023:7772 · 66 productsRed Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.

Advisories and patches

www.postgresql.orgRelease Notes
www.postgresql.orgVendor Advisory

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

CNACVSS 3.18.8read 2026-10-23
NVDCVSS 3.18.8read 2026-10-23
CNAweakness (CWE)CWE-190read 2026-10-23
NVDweakness (CWE)CWE-190read 2026-10-23
FIRST EPSSEPSS score4.3 %2026-10-22

Technical details

CVSS v3 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published: 2023-12-10
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2023-5869?

Is CVE-2023-5869 actively exploited?

Active exploitation of CVE-2023-5869 has not been confirmed. Its EPSS score was 4.3% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2023-5869?

CVE-2023-5869 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running postgresql:12? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database