OESA-2025-2141 (CVE-2025-8713)
Vulnerability from osv_openeuler – Published: 2025-09-05 11:09 – Updated: 2026-08-06 11:09 – Source websitePostgreSQL is an advanced Object-Relational database management system (DBMS). The base postgresql package contains the client programs that you'll need to access a PostgreSQL DBMS server, as well as HTML documentation for the whole system. These client programs can be located on the same machine as the PostgreSQL server, or on a remote machine that accesses a PostgreSQL server over a network connection. The PostgreSQL server can be found in the postgresql-server sub-package.
Security Fix(es):
PostgreSQL optimizer statistics allow a user to read sampled data within a view that the user cannot access. Separately, statistics allow a user to read sampled data that a row security policy intended to hide. PostgreSQL maintains statistics for tables by sampling data available in columns; this data is consulted during the query planning process. Prior to this release, a user could craft a leaky operator that bypassed view access control lists (ACLs) and bypassed row security policies in partitioning or table inheritance hierarchies. Reachable statistics data notably included histograms and most-common-values lists. CVE-2017-7484 and CVE-2019-10130 intended to close this class of vulnerability, but this gap remained. Versions before PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 are affected.(CVE-2025-8713)
Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql meta-commands. pg_dumpall is also affected. pg_restore is affected when used to generate a plain-format dump. This is similar to MySQL CVE-2024-21096. Versions before PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 are affected.(CVE-2025-8714)
Improper neutralization of newlines in pg_dump in PostgreSQL allows a user of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql meta-commands inside a purpose-crafted object name. The same attacks can achieve SQL injection as a superuser of the restore target server. pg_dumpall, pg_restore, and pg_upgrade are also affected. Versions before PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 are affected. Versions before 11.20 are unaffected. CVE-2012-0868 had fixed this class of problem, but version 11.20 reintroduced it.(CVE-2025-8715)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"postgresql-13.22-1.oe2203sp3.aarch64.rpm",
"postgresql-contrib-13.22-1.oe2203sp3.aarch64.rpm",
"postgresql-debuginfo-13.22-1.oe2203sp3.aarch64.rpm",
"postgresql-debugsource-13.22-1.oe2203sp3.aarch64.rpm",
"postgresql-docs-13.22-1.oe2203sp3.aarch64.rpm",
"postgresql-llvmjit-13.22-1.oe2203sp3.aarch64.rpm",
"postgresql-plperl-13.22-1.oe2203sp3.aarch64.rpm",
"postgresql-plpython3-13.22-1.oe2203sp3.aarch64.rpm",
"postgresql-pltcl-13.22-1.oe2203sp3.aarch64.rpm",
"postgresql-private-devel-13.22-1.oe2203sp3.aarch64.rpm",
"postgresql-private-libs-13.22-1.oe2203sp3.aarch64.rpm",
"postgresql-server-13.22-1.oe2203sp3.aarch64.rpm",
"postgresql-server-devel-13.22-1.oe2203sp3.aarch64.rpm",
"postgresql-static-13.22-1.oe2203sp3.aarch64.rpm",
"postgresql-test-13.22-1.oe2203sp3.aarch64.rpm"
],
"noarch": [
"postgresql-test-rpm-macros-13.22-1.oe2203sp3.noarch.rpm"
],
"src": [
"postgresql-13.22-1.oe2203sp3.src.rpm"
],
"x86_64": [
"postgresql-13.22-1.oe2203sp3.x86_64.rpm",
"postgresql-contrib-13.22-1.oe2203sp3.x86_64.rpm",
"postgresql-debuginfo-13.22-1.oe2203sp3.x86_64.rpm",
"postgresql-debugsource-13.22-1.oe2203sp3.x86_64.rpm",
"postgresql-docs-13.22-1.oe2203sp3.x86_64.rpm",
"postgresql-llvmjit-13.22-1.oe2203sp3.x86_64.rpm",
"postgresql-plperl-13.22-1.oe2203sp3.x86_64.rpm",
"postgresql-plpython3-13.22-1.oe2203sp3.x86_64.rpm",
"postgresql-pltcl-13.22-1.oe2203sp3.x86_64.rpm",
"postgresql-private-devel-13.22-1.oe2203sp3.x86_64.rpm",
"postgresql-private-libs-13.22-1.oe2203sp3.x86_64.rpm",
"postgresql-server-13.22-1.oe2203sp3.x86_64.rpm",
"postgresql-server-devel-13.22-1.oe2203sp3.x86_64.rpm",
"postgresql-static-13.22-1.oe2203sp3.x86_64.rpm",
"postgresql-test-13.22-1.oe2203sp3.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP3",
"name": "postgresql",
"purl": "pkg:rpm/openEuler/postgresql\u0026distro=openEuler-22.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "13.22-1.oe2203sp3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "PostgreSQL is an advanced Object-Relational database management system (DBMS).\nThe base postgresql package contains the client programs that you\u0026amp;apos;ll need to\naccess a PostgreSQL DBMS server, as well as HTML documentation for the whole\nsystem. These client programs can be located on the same machine as the\nPostgreSQL server, or on a remote machine that accesses a PostgreSQL server\nover a network connection. The PostgreSQL server can be found in the\npostgresql-server sub-package.\r\n\r\nSecurity Fix(es):\n\nPostgreSQL optimizer statistics allow a user to read sampled data within a view that the user cannot access. Separately, statistics allow a user to read sampled data that a row security policy intended to hide. PostgreSQL maintains statistics for tables by sampling data available in columns; this data is consulted during the query planning process. Prior to this release, a user could craft a leaky operator that bypassed view access control lists (ACLs) and bypassed row security policies in partitioning or table inheritance hierarchies. Reachable statistics data notably included histograms and most-common-values lists. CVE-2017-7484 and CVE-2019-10130 intended to close this class of vulnerability, but this gap remained. Versions before PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 are affected.(CVE-2025-8713)\n\nUntrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql meta-commands. pg_dumpall is also affected. pg_restore is affected when used to generate a plain-format dump. This is similar to MySQL CVE-2024-21096. Versions before PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 are affected.(CVE-2025-8714)\n\nImproper neutralization of newlines in pg_dump in PostgreSQL allows a user of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql meta-commands inside a purpose-crafted object name. The same attacks can achieve SQL injection as a superuser of the restore target server. pg_dumpall, pg_restore, and pg_upgrade are also affected. Versions before PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 are affected. Versions before 11.20 are unaffected. CVE-2012-0868 had fixed this class of problem, but version 11.20 reintroduced it.(CVE-2025-8715)",
"id": "OESA-2025-2141",
"modified": "2026-08-06T11:09:13Z",
"published": "2025-09-05T11:09:13Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-2141"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-8713"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-8714"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-8715"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "postgresql security update",
"upstream": [
"CVE-2025-8713",
"CVE-2025-8714",
"CVE-2025-8715"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.