Skip to main content
No exploitation reportedFix available

CVE-2018-10915

No exploitation reported by the sources we read.

  • Published2018-08-09
  • Fixed in10.5 · 9.6.10 · 9.5.14 · 9.4.19 · 9.3.24
  • WeaknessCWE-200 · CWE-665 · CWE-89

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 vulnerability was found in libpq, the default PostgreSQL client library where libpq failed to properly reset its internal state between connections. If an affected version of libpq was used with "host" or "hostaddr" connection parameters from untrusted input, attackers could bypass client-side connection security features, obtain access to higher privileged connections or potentially cause other impact through SQL injection, by causing the PQescape() functions to malfunction. Postgresql versions before 10.5, 9.6.10, 9.5.14, 9.4.19, and 9.3.24 are affected.

Timeline

dates in UTC
  1. 2018-08-0920:29CVE 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-2018-10915?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2018-10915?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
PostgreSQL
BranchAffectedFixed in
10.x≥ 10.0, < 10.510.5
9.6≥ 9.6.0, < 9.6.109.6.10
9.5≥ 9.5.0, < 9.5.149.5.14
9.4≥ 9.4.0, < 9.4.199.4.19
9.3≥ 9.3.0, < 9.3.249.3.24
Canonical ubuntu linux
BranchAffectedFixed in
14.4= 14.04no fix published
16.4= 16.04no fix published
18.4= 18.04no fix published
Debian debian linux
BranchAffectedFixed in
8.0= 8.0no fix published
9.0= 9.0no fix published

6 more products in the sources.

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

Fix

  1. Update PostgreSQL to 10.5 · 9.6.10 · 9.5.14 · 9.4.19 · 9.3.24

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CNACVSS 3.08.5read 2026-10-23
  • NVDCVSS 3.07.5read 2026-10-23
  • NVDCVSS 2.06read 2026-10-23
  • CNAweakness (CWE)CWE-200, CWE-665, CWE-89read 2026-10-23
  • NVDweakness (CWE)CWE-89read 2026-10-23
  • FIRST EPSSEPSS score5.1 %2026-10-22

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2018-08-09
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2018-10915?

A vulnerability was found in libpq, the default PostgreSQL client library where libpq failed to properly reset its internal state between connections. If an affected version of libpq was used with "host" or "hostaddr" connection parameters from untrusted input, attackers could bypass client-side connection security features, obtain access to higher privileged connections or potentially cause other impact through SQL injection, by causing the PQescape() functions to malfunction. Postgresql versions before 10.5, 9.6.10, 9.5.14, 9.4.19, and 9.3.24 are affected.

Is CVE-2018-10915 actively exploited?

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

What is the CVSS score for CVE-2018-10915?

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

Running libpq? 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 ».

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