CVE-2026-2360
Raw vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-2360 is a high-severity Uncontrolled Search Path Element (CWE-427) vulnerability in Postgresql (inferred from references). Its CVSS base score is 8.0 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception (T1034); ranked at the 34th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-2360 is a privilege escalation vulnerability in PostgreSQL Anonymizer, a PostgreSQL extension. It enables a user to gain superuser privileges by creating a custom operator in the public schema containing malicious code, which is later executed with superuser privileges during extension creation. The vulnerability carries a CVSS v3.1 base score of 8.0 (AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H) and is associated with CWE-427 (Untrusted Search Path). Risk is elevated in PostgreSQL 14 or instances upgraded from PostgreSQL 14 or earlier versions.
An attacker with high privileges required to create objects in the public schema can exploit this by planting the malicious operator, leading to arbitrary code execution as superuser upon extension installation. In PostgreSQL 15 and later, public schema creation permissions are revoked by default, limiting exploitation to scenarios where a superuser explicitly adds a schema to their search_path and grants CREATE privileges to untrusted users—actions discouraged by PostgreSQL documentation.
The issue is fixed in PostgreSQL Anonymizer version 3.0.1 and later, as detailed in the project's NEWS.md and issue tracker. PostgreSQL documentation on schemas reinforces best practices to avoid granting CREATE on public or custom schemas to untrusted users.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-5937
Vulnerability Data
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…
more
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
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
Establishes restrictive configuration settings that can define and lock down approved search paths.
Enforces approved authorizations so that only intended actors can place or modify elements in the search path.
Limits privileges so unintended actors cannot write to or control directories in the product's search path.
Restricts logical and physical access to change system configuration, including search-path settings and directories.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices directly address design of search paths and resource loading.
Hardened configuration baselines can enforce safe search-path settings and reduce exposure.
Execution allow-listing can block malicious binaries placed in hijackable search locations.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect uncontrolled search-path issues but does not prevent them by itself.
Restricting software installation reduces the chance that an attacker-controlled path element is introduced into the search path.
Secure system architecture and engineering principles require explicit control over search paths and resource locations.
Secure coding practices directly address the use of fixed or controlled search paths that can be influenced by unintended actors.
Configuration management can enforce approved search-path settings but does not inherently prevent the weakness.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248577 OL 8 must enable kernel parameters to enforce Discretionary Access Control (DAC) on symlinks. prevents CWE-427