CVE-2019-10127 [High] | Security Bypass in Postgresql

A vulnerability was found in postgresql versions 11.x prior to 11.3. The Windows installer for BigSQL-supplied PostgreSQL does not lock down the ACL of the binary installation directory or the ACL of the data directory; it keeps the inherited ACL. In the default configuration, an attacker having both an unprivileged Windows account and an unprivileged PostgreSQL account can cause the PostgreSQL service account to execute arbitrary code. An attacker having only the unprivileged Windows account can read arbitrary data directory files, essentially bypassing database-imposed read access limitations. An attacker having only the unprivileged Windows account can also delete certain data directory files.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.07%	0.32%	+0.25%
2	2025-03-17	0.04%	0.07%	+0.02%
3	2023-03-07	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.07%

0.32%

+0.25%

2025-03-17

0.04%

0.07%

+0.02%

2023-03-07

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. 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:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.0	6.0	[email protected]
4.3	2.0	MEDIUM	`AV:L/AC:L/Au:S/C:P/I:P/A:P` Click to expand Access vector (AV:L) Requires local access to the target system. 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:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	3.1	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.0

6.0

[email protected]

4.3

2.0

MEDIUM

AV:L/AC:L/Au:S/C:P/I:P/A:P Click to expand

Access vector (AV:L): Requires local access to the target system.
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:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

3.1

6.4

[email protected]

OS Trackers for CVE-2019-10127

vendor	priority	summary	link
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2019-10127
`ubuntu`	medium	CVE-2019-10127 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, not-affected 6, needs-triage 4.	https://ubuntu.com/security/CVE-2019-10127

Affected software / configurations for CVE-2019-10127

Vendor	Product	Version	Raw CPE
postgresql	postgresql	< 9.4.22	cpe:2.3:a:postgresql:postgresql::::::::
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::::::::

References for CVE-2019-10127

URL	Tags
https://bugzilla.redhat.com/show_bug.cgi?id=1707098	Issue Tracking Third Party Advisory
https://security.netapp.com/advisory/ntap-20210430-0004/	Third Party Advisory
https://www.postgresql.org/about/news/1939/	Patch Release Notes Vendor Advisory

URL

CVE-2019-10127

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

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

Weakness enumeration for CVE-2019-10127

OS Trackers for CVE-2019-10127

Affected software / configurations for CVE-2019-10127

References for CVE-2019-10127