CVE-2019-10130

A vulnerability was found in PostgreSQL versions 11.x up to excluding 11.3, 10.x up to excluding 10.8, 9.6.x up to, excluding 9.6.13, 9.5.x up to, excluding 9.5.17. PostgreSQL maintains column statistics for tables. Certain statistics, such as histograms and lists of most common values, contain values taken from the column. PostgreSQL does not evaluate row security policies before consulting those statistics during query planning; an attacker can exploit this to read the most common values of certain columns. Affected columns are those for which the attacker has SELECT privilege and for which, in an ordinary query, row-level security prunes the set of rows visible to the attacker.

Published: 2019-07-30 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-10130 is rated Low Risk (34.2/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.25%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-10130

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-26 0.24% 0.25% +0.01%
2 2025-10-29 0.25% 0.24% -0.01%
3 2025-10-21 — 0.25% —

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-10130

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 1.4 [email protected]
3.1 3.0 LOW
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.6 1.4 [email protected]
4.0 2.0 MEDIUM
AV:N/AC:L/Au:S/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.0 2.9 [email protected]

Weakness enumeration for CVE-2019-10130

OS Trackers for CVE-2019-10130

vendor priority summary link
alpine medium CVE-2019-10130: 3 source package rows (postgresql, postgresql14, postgresql15); 24 state rows across 11 repos (3.10-main, 3.11-main, 3.12-main, 3.17-main, 3.18-main, 3.19-community, 3.19-main, 3.20-community, 3.20-main, edge-community, edge-main); fixed 16, open 8. https://security.alpinelinux.org/vuln/CVE-2019-10130
gentoo normal CVE-2019-10130: 1 GLSA(s) (202003-03), 1 atom(s) (dev-db/postgresql); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2019-10130
redhat low — https://access.redhat.com/security/cve/CVE-2019-10130
suse medium CVE-2019-10130 severity moderate: SUSE including 179 source package names (10.19:postgresql10-10.9-8.3.1, 10.19:postgresql10-server-10.9-8.3.1, …), 344 product×package rows across 43 product lines (Container suse/postgres, SLES for SAP Applications 11 SP3, … (43 product lines)): Fixed 285, Known Not Affected 59. https://www.suse.com/security/cve/CVE-2019-10130/
ubuntu medium CVE-2019-10130 medium priority: Ubuntu including 5 source packages (postgresql-10, postgresql-11, postgresql-9.1, postgresql-9.3, postgresql-9.5), 30 status rows across 6 suites (bionic, cosmic, disco, trusty, upstream, xenial): DNE 20, released 7, needs-triage 2, not-affected 1. https://ubuntu.com/security/CVE-2019-10130

Affected software / configurations for CVE-2019-10130

Vendor Product Version Raw CPE
postgresql postgresql >= 9.5.0, < 9.5.17 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 9.6.0, < 9.6.13 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 10.0, < 10.8 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
postgresql postgresql >= 11.0, < 11.3 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
opensuse leap 15.1 cpe:2.3:o:opensuse:leap:15.1:*:*:*:*:*:*:*

References for CVE-2019-10130

cvelogic Threat Intelligence