CVE-2016-5424

CVE-2016-5424 is a high-severity vulnerability in Postgresql with a CVSS 3.x base score of 7.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-94.

Key facts

• Severity: High (CVSS 3.x base score 7.1)
• CVSS v2: 4.6
• EPSS exploit prediction: 5% (91st percentile)
• Actively exploited: Not listed in CISA KEV
• Weakness: CWE-94
• Affected product: Postgresql
• Published: 2016-12-09
• Last modified: 2026-06-17

Description

PostgreSQL before 9.1.23, 9.2.x before 9.2.18, 9.3.x before 9.3.14, 9.4.x before 9.4.9, and 9.5.x before 9.5.4 might allow remote authenticated users with the CREATEDB or CREATEROLE role to gain superuser privileges via a (1) " (double quote), (2) \ (backslash), (3) carriage return, or (4) newline character in a (a) database or (b) role name that is mishandled during an administrative operation.

Frequently asked questions

What is CVE-2016-5424?

PostgreSQL before 9.1.23, 9.2.x before 9.2.18, 9.3.x before 9.3.14, 9.4.x before 9.4.9, and 9.5.x before 9.5.4 might allow remote authenticated users with the CREATEDB or CREATEROLE role to gain superuser privileges via a (1) " (double quote), (2) \ (backslash), (3) carriage return, or (4) newline character in a (a) database or (b) role name that is mishandled during an administrative operation.

How severe is CVE-2016-5424?

CVE-2016-5424 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over network with high attack complexity, requires low privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2016-5424 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 5% (91st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2016-5424?

CVE-2016-5424 primarily affects Postgresql. In total, 47 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2016-5424?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2016-5424 published?

CVE-2016-5424 was published on 2016-12-09 and last updated on 2026-06-17.

References

• http://rhn.redhat.com/errata/RHSA-2016-1781.html
• http://rhn.redhat.com/errata/RHSA-2016-1820.html
• http://rhn.redhat.com/errata/RHSA-2016-1821.html
• http://rhn.redhat.com/errata/RHSA-2016-2606.html
• http://www.debian.org/security/2016/dsa-3646
• http://www.securityfocus.com/bid/92435
• http://www.securitytracker.com/id/1036617
• https://access.redhat.com/errata/RHSA-2017:2425
• https://security.gentoo.org/glsa/201701-33
• https://www.postgresql.org/about/news/1688/
• https://www.postgresql.org/docs/current/static/release-9-1-23.html
• https://www.postgresql.org/docs/current/static/release-9-2-18.html
• https://www.postgresql.org/docs/current/static/release-9-3-14.html
• https://www.postgresql.org/docs/current/static/release-9-4-9.html
• https://www.postgresql.org/docs/current/static/release-9-5-4.html

Affected products (47)

• cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.1:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.2:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.3:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.4:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.5:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.6:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.7:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.8:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.9:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.10:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.11:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.12:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.13:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.14:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.15:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.16:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.2.17:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.3:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.3.1:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.3.2:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.3.3:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.3.4:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.3.5:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.3.6:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.3.7:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.3.8:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.3.9:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.3.10:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.3.11:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.3.12:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.3.13:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.4:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.4.1:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.4.2:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.4.3:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.4.4:*:*:*:*:*:*:*
• cpe:2.3:a:postgresql:postgresql:9.4.5:*:*:*:*:*:*:*

More vulnerabilities in Postgresql

• CVE-2013-1903 — Critical (CVSS 10.0): PostgreSQL, possibly 9.2.x before 9.2.4, 9.1.x before 9.1.9, 9.0.x before 9.0.13, 8.4.x before 8.4.17, and 8.3.x before…
• CVE-2013-1902 — Critical (CVSS 10.0): PostgreSQL, 9.2.x before 9.2.4, 9.1.x before 9.1.9, 9.0.x before 9.0.13, 8.4.x before 8.4.17, and 8.3.x before 8.3.23…
• CVE-2007-3279 — Critical (CVSS 10.0): PostgreSQL 8.1 and probably later versions, when the PL/pgSQL (plpgsql) language has been created, grants certain…
• CVE-2002-1399 — Critical (CVSS 10.0): Unknown vulnerability in cash_out and possibly other functions in PostgreSQL 7.2.1 and earlier, and possibly later…
• CVE-2015-0244 — Critical (CVSS 9.8): PostgreSQL before 9.0.19, 9.1.x before 9.1.15, 9.2.x before 9.2.10, 9.3.x before 9.3.6, and 9.4.x before 9.4.1 does not…
• CVE-2015-3166 — Critical (CVSS 9.8): The snprintf implementation in PostgreSQL before 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11, 9.3.x before 9.3.7,…

All CVEs affecting Postgresql →

Other CWE-94 (Code Injection) vulnerabilities

• CVE-2026-57624 — Critical (CVSS 10.0): Unauthenticated Remote Code Execution (RCE) in Blocksy Companion Pro <= 2.1.46 versions.
• CVE-2026-10134 — Critical (CVSS 10.0): IBM Langflow OSS 1.0.0 through 1.9.3 allows an attacker to read every secret available to the Langflow process, read…
• CVE-2026-53576 — Critical (CVSS 10.0): Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter…
• CVE-2026-10561 — Critical (CVSS 10.0): IBM Langflow OSS 1.0.0 through 1.9.3 has an vulnerability due to an improper isolation of Python execution combined…
• CVE-2026-25470 — Critical (CVSS 10.0): Improper Control of Generation of Code ('Code Injection') vulnerability in ACPT ACPT (Pro) - Custom Post Types Plugin…
• CVE-2026-48836 — Critical (CVSS 10.0): Unauthenticated Remote Code Execution (RCE) in Easy Invoice <= 2.1.19 versions.

Browse all CWE-94 (Code Injection) vulnerabilities →