CVE-2020-14349

What it is

It was found that PostgreSQL versions before 12.4, before 11.9 and before 10.14 did not properly sanitize the search_path during logical replication. An authenticated attacker could use this flaw in an attack similar to CVE-2018-1058, in order to execute arbitrary SQL command in the context of the user used for replication.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account, but needs a user to act. High risk of data exposure, data tampering, service disruption.

Exploit odds

2.2% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2020-08-24 13:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:54 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 2.2% in the next 30 days (EPSS).
• Severity: 7.1 HIGH (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2020-08-24 13:15 UTC

Last modified

2026-06-17 02:54 UTC

Exploit probability

2.2% · EPSS, next 30 days

Weakness

CWE-89 · SQL injection

Record status

Modified

Affected

• PostgreSQL < 10.14
• PostgreSQL < 11.9
• PostgreSQL < 12.4
• Opensuse Leap 15.1
• Opensuse Leap 15.2

Attack profile CVSS 3.1 · 7.1

Attack vector

Network

Complexity

High

Privileges needed

Low

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-14349.md and follow it. Check whether this project is affected by CVE-2020-14349. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge