CVE-2017-15099

What it is

INSERT ... ON CONFLICT DO UPDATE commands in PostgreSQL 10.x before 10.1, 9.6.x before 9.6.6, and 9.5.x before 9.5.10 disclose table contents that the invoker lacks privilege to read. These exploits affect only tables where the attacker lacks full read access but has both INSERT and UPDATE privileges. Exploits bypass row level security policies and lack of SELECT privilege.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data exposure.

Exploit odds

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

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2017-11-22 18:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 01:07 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 6.3% in the next 30 days (EPSS).
• Severity: 6.5 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2017-11-22 18:29 UTC

Last modified

2026-06-17 01:07 UTC

Exploit probability

6.3% · EPSS, next 30 days

Weakness

CWE-200 · Information exposure

Record status

Modified

Affected

• PostgreSQL 9.5
• PostgreSQL 9.5.1
• PostgreSQL 9.5.2
• PostgreSQL 9.5.3
• PostgreSQL 9.5.4
• PostgreSQL 9.5.5
• PostgreSQL 9.5.6
• PostgreSQL 9.5.7

Attack profile CVSS 3.0 · 6.5

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

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-2017-15099.md and follow it. Check whether this project is affected by CVE-2017-15099. 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