LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2005: PostgreSQL pgcrypto heap buffer overflow executes arbitrary code

Heap buffer overflow in PostgreSQL pgcrypto allows a ciphertext provider to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-2005 is a PostgreSQL pgcrypto memory corruption flaw. A user who can supply ciphertext to vulnerable pgcrypto processing may be able to run code as the database operating-system account. That can compromise data confidentiality, integrity, and availability.

Executive priority

Prioritize remediation for internet-facing or multi-tenant databases first. This is high urgency because successful exploitation can execute code as the database OS user, but the provided evidence does not prove active exploitation.

Technical view

The source describes a heap buffer overflow in PostgreSQL pgcrypto, mapped to CWE-120 and CWE-122. Affected releases are before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21. CVSS 3.1 is 8.8 with network attack vector, low privileges, no user interaction, and high CIA impact.

Likely exposure

Exposure is most likely where PostgreSQL uses pgcrypto and accepts ciphertext from authenticated users, applications, tenants, or integrations. Systems below the fixed PostgreSQL versions should be treated as affected unless vendor packaging says otherwise.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates exploitation requires low privileges and no user interaction, but the bundle does not provide public exploit maturity or detailed preconditions beyond ciphertext provision.

Researcher notes

Focus validation on pgcrypto presence, reachable ciphertext-processing paths, authentication boundaries, and vendor package status. Avoid assuming all PostgreSQL databases are exploitable; pgcrypto use and attacker ability to influence ciphertext are important exposure qualifiers.

Mitigation direction

  • Upgrade PostgreSQL to 18.2, 17.8, 16.12, 15.16, 14.21, or later.
  • Apply relevant vendor updates, including Red Hat errata where applicable.
  • Confirm distribution packages backport the pgcrypto fix if version strings differ.
  • Restrict untrusted access to pgcrypto-dependent workflows until patched.
  • Review database OS account privileges and harden containment around PostgreSQL.

Validation and detection

  • Inventory PostgreSQL versions across managed, self-hosted, and containerized deployments.
  • Check whether the pgcrypto extension is installed or used by applications.
  • Compare installed versions against the fixed PostgreSQL release thresholds.
  • Verify vendor advisory status for Red Hat or downstream packages.
  • Review monitoring for unexplained PostgreSQL crashes around pgcrypto workloads.
Prepared
Confidence
high
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-120: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-122: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2005 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
35Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9PostgreSQL
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-2005Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPpostgresql: PostgreSQL pgcrypto heap buffer overflow executes arbitrary code
other:Red Hat severity ratingcvssV3_1
  • 2026-02-12T14:01:34.491Z: Reported to Red Hat.
  • 2026-02-12T13:00:09.784Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aPostgreSQL18, 17, 16, 15, 0unaffected
Weakness

CWE details

CWE-120CWE-122

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.