CVE-2016-2193

PostgreSQL before 9.5.x before 9.5.2 does not properly maintain row-security status in cached plans, which might allow attackers to bypass intended access restrictions by leveraging a session that performs queries as more than one role.

Published: 2016-04-11 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2016-2193 is rated Moderate Risk (56.8/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.81%). Review affected assets and schedule remediation.

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-2016-2193

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-06-15 1.53% 1.81% +0.28%
2 2025-04-12 0.91% 1.53% +0.62%
3 2025-04-10 — 0.91% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-2193

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:N)
No account or special rights needed—anonymous or random user is enough.
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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:P/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:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2016-2193

OS Trackers for CVE-2016-2193

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2016-2193
suse medium CVE-2016-2193 severity moderate: SUSE including 56 source package names (libecpg6-10.10-1.15.1, libecpg6-10.5-1.3.1, …), 291 product×package rows across 49 product lines (HPE Helion OpenStack 8, SUSE CaaS Platform 4.0, … (49 product lines)): Known Not Affected 219, Fixed 72. https://www.suse.com/security/cve/CVE-2016-2193/
ubuntu medium CVE-2016-2193 medium priority: Ubuntu including 5 source packages (postgresql-8.4, postgresql-9.1, postgresql-9.3, postgresql-9.4, postgresql-9.5), 20 status rows across 4 suites (precise, trusty, upstream, wily): DNE 11, not-affected 8, released 1. https://ubuntu.com/security/CVE-2016-2193

Affected software / configurations for CVE-2016-2193

Vendor Product Version Raw CPE
postgresql postgresql 9.5 cpe:2.3:a:postgresql:postgresql:9.5:*:*:*:*:*:*:*
postgresql postgresql 9.5.1 cpe:2.3:a:postgresql:postgresql:9.5.1:*:*:*:*:*:*:*

References for CVE-2016-2193

cvelogic Threat Intelligence