dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2026-2361

HIGH · 8.0 CVSS v3.1 Published 2026-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
PostgreSQL Anonymizer contains a vulnerability that allows a user to gain superuser privileges by creating a temporary view based on a function containing malicious code. When the anon.get_tablesample_ratio function is then called, the malicious code is executed with superuser privileges. This privilege elevation can be exploited by users having the CREATE privilege in PostgreSQL 15 and later. The risk is higher with PostgreSQL 14 or with instances upgraded from PostgreSQL 14 or a prior version because the creation permission on the public schema is granted by default. The problem is resolved in PostgreSQL Anonymizer 3.0.1 and further versions

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

PostgreSQL Anonymizer has a privilege escalation vulnerability where users with CREATE privilege can create a temporary view containing malicious code within a function. When the anon.get_tablesample_ratio function is executed, the malicious code runs with superuser privileges, allowing complete database compromise.

MitigationUpgrade to PostgreSQL Anonymizer 3.0.1 or later. Additionally, review and restrict CREATE privileges on schemas, particularly the public schema, especially on PostgreSQL 14 or upgraded instances where public schema permissions are granted by default.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm PostgreSQL Anonymizer extension is installed
    Run: SELECT * FROM pg_extension WHERE extname = 'anon';
    Affected if No rows returned means the extension is not installed and the vulnerability does not apply.
  2. Check the installed version of PostgreSQL Anonymizer
    Run: SELECT * FROM pg_extension WHERE extname = 'anon'; and look at the extversion column, or run: SELECT anon.version();
    Affected if Version is lower than 3.0.1 (e.g., 3.0.0 or earlier).
  3. Verify current user has CREATE privilege on any schema
    Run: SELECT schema_name, privilege_type FROM information_schema.schema_privileges WHERE grantee = CURRENT_USER AND privilege_type = 'CREATE';
    Affected if Any rows returned means the user has CREATE privilege on at least one schema.
  4. Check if the public schema allows CREATE for non-superusers
    Run: SELECT has_schema_privilege('public', 'CREATE') AS public_create_privilege;
    Affected if Returns true - the public schema grants CREATE privilege, which allows the attack.
  5. Look for the get_tablesample_ratio function in the anon schema
    Run: SELECT proname, pronamespace::regnamespace FROM pg_proc WHERE proname = 'get_tablesample_ratio' AND pronamespace = 'anon'::regnamespace;
    Affected if Function exists - the vulnerable function is present in the environment.

If PostgreSQL Anonymizer version is below 3.0.1 AND the current user has CREATE privilege on any schema (especially public), the environment is vulnerable to privilege escalation via the get_tablesample_ratio function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to PostgreSQL Anonymizer 3.0.1 or later. Additionally, review and restrict CREATE privileges on schemas, particularly the public schema, especially on PostgreSQL 14 or upgraded instances where public schema permissions are granted by default.

Recommended fix High confidence

PostgreSQL Anonymizer 3.0.1 or later

  1. Upgrade PostgreSQL Anonymizer to version 3.0.1 or a later release

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2361 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2361 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data