Skip to content
Heist/ feed
Back to feed
High

Improper search_path protection in PostgreSQL Anonymizer 2.5 allows any user to gain superuser privileges in PostgreSQL 14

Type: advisorySources: OSV

PostgreSQL Anonymizer contains a vulnerability that allows a user to gain superuser privileges by creating a custom operator in the public schema and place malicious code in that operator. This operator will later be executed with superuser privileges when the extension is created. The risk is higher with PostgreSQL 14 or with instances upgraded from PostgreSQL 14 or a prior version. With PostgreSQL 15 and later, the creation permission on the public schema is revoked by default and this exploit can only be achieved if a superuser adds a new schema in her/his own search_path and grants the CREATE privilege on that schema to untrusted users, both actions being clearly discouraged by the PostgreSQL documentation. The problem is resolved in PostgreSQL Anonymizer 3.0.1 and further versions

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2026-2360
Confirmed fixed CVEs
Not specified
Updated in this feed
5 Nov 2026, 23:56 UTC · Revision 1

Source evidence

Improper search_path protection in PostgreSQL Anonymizer 2.5 allows any user to gain superuser privileges in PostgreSQL 14

core-osv · Original source

Published 11 Feb 2026, 17:47 UTC

PostgreSQL Anonymizer contains a vulnerability that allows a user to gain superuser privileges by creating a custom operator in the public schema and place malicious code in that operator. This operator will later be executed with superuser privileges when the extension is created. The risk is higher with PostgreSQL 14 or with instances upgraded from PostgreSQL 14 or a prior version. With PostgreSQL 15 and later, the creation permission on the public schema is revoked by default and this exploit can only be achieved if a superuser adds a new schema in her/his own search_path and grants the CREATE privilege on that schema to untrusted users, both actions being clearly discouraged by the PostgreSQL documentation. The problem is resolved in PostgreSQL Anonymizer 3.0.1 and further versions

osv:CVE-2026-2360
Complete source record
{
  "id": "80bf16e890af1558e24fc5353051d8069a8749071bef309ed8a255aa6e83f0d0",
  "url": "https://osv.dev/vulnerability/CVE-2026-2360",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "Improper search_path protection in PostgreSQL Anonymizer 2.5 allows any user to gain superuser privileges in PostgreSQL 14",
    "summary": "PostgreSQL Anonymizer contains a vulnerability that allows a user to gain superuser privileges by creating a custom operator in the public schema and place malicious code in that operator. This operator will later be executed with superuser privileges when the extension is created. The risk is higher with PostgreSQL 14 or with instances upgraded from PostgreSQL 14 or a prior version. With PostgreSQL 15 and later, the creation permission on the public schema is revoked by default and this exploit can only be achieved if a superuser adds a new schema in her/his own search_path and grants the CREATE privilege on that schema to untrusted users, both actions being clearly discouraged by the PostgreSQL documentation. The problem is resolved in PostgreSQL Anonymizer 3.0.1 and further versions",
    "evidence": "osv:CVE-2026-2360",
    "products": [],
    "severity": "high",
    "structured": {
      "id": "CVE-2026-2360",
      "aliases": [
        "CVE-2026-2360"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://gitlab.com/dalibo/postgresql_anonymizer",
              "type": "GIT",
              "events": [
                {
                  "introduced": "c79d5b610629a197f1eb4c868168c8cba9db4868"
                },
                {
                  "fixed": "b13a74ad3fe6b95c15aae6055d25e4669f7f2920"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "range": [
                      {
                        "introduced": "1"
                      },
                      {
                        "fixed": "3.0.1"
                      }
                    ],
                    "source": "AFFECTED_FIELD",
                    "strategy": "StandardRange"
                  }
                ]
              }
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-2360.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:45.349945869Z",
      "provider": "osv",
      "references": [
        "https://gitlab.com/dalibo/postgresql_anonymizer/-/blob/latest/NEWS.md",
        "https://www.postgresql.org/docs/current/ddl-schemas.html#DDL-SCHEMAS-PATH",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/2xxx/CVE-2026-2360.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-2360",
        "https://gitlab.com/dalibo/postgresql_anonymizer/-/issues/616"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-427"
        ],
        "cna_assigner": "PostgreSQL",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/2xxx/CVE-2026-2360.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-2360",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 513258,
  "published_at": "2026-02-11T17:47:55.737+00:00"
}