MediumCVE-2026-50735

    EnterpriseDB pglogical: Out-of-bounds Read (CVE-2026-50735)

    Published Last modified Sources: EUVD, CVE.org

    Share

    What is affected, what to do

    pglogical's apply worker does not sufficiently validate the length of certain fields in incoming replication protocol messages before copying them, resulting in an out-of-bounds read. A party acting as the publisher for a subscription, for example a non-PostgreSQL endpoint that speaks the pglogical replication protocol, can return crafted messages that cause the subscriber's apply worker to read beyond the bounds of an allocated buffer, disclosing adjacent process memory or crashing the worker.

    Update EnterpriseDB pglogical to version 2.4.8.

    Affected
    • pgEdge Spock lte 4..4.1.0.3
    • pgEdge Spock lte 5..5.0.11
    • EnterpriseDB pglogical lt 2..2.4.8
    • pgEdge Spock lte 3..3.3.6
    Fixed in
    • EnterpriseDB pglogical 2.4.8

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    6.8

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    6.8

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: EUVD, CVE.org

    0.4 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 32.0

    Show all metrics
    Severity
    Medium
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    62.87 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    6.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    6.8
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    6.1
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.4 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    32.0
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 28 July 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-125

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    pglogical's apply worker does not sufficiently validate the length of certain fields in incoming replication protocol messages before copying them, resulting in an out-of-bounds read. A party acting as the publisher for a subscription, for example a non-PostgreSQL endpoint that speaks the pglogical replication protocol, can return crafted messages that cause the subscriber's apply worker to read beyond the bounds of an allocated buffer, disclosing adjacent process memory or crashing the worker. To exploit the issue an attacker must be able to direct a subscription at an endpoint they control. In default installations this requires privileges normally reserved for a superuser, so the issue is most relevant to managed deployments where the ability to create subscriptions has been delegated to non-superuser roles.

    Source: ENISA EUVD, cvelistv5, NVD (NIST), CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    EnterpriseDBpglogical
    • 2 – < 2.4.8
    • 2.4.8
    pgEdgeSpock
    • 3 – ≤ 3.3.6
    • 4 – ≤ 4.1.0.3
    • 5 – ≤ 5.0.11
    • —
    • —
    • —
    enterprisedbpglogical
    • 2.0.0 – < 2.4.8
    • 2.4.8

    Vendors and products

    Weakness classes (CWE)

    • CWE-125Out-of-bounds Read

      Base

      The product reads data past the end, or before the beginning, of the intended buffer.

      Entry at MITRE CWE-125

    References & sources

    • enterprisedb.comdocs/security/advisories/cve202650735Vendor advisory, euvd
    • github.compgEdge/spock/security/advisories/GHSA-j2m3-f88h-2h46Vendor advisory

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modified20be33e2…

      Show 5 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)added
      —
      Affected value modified. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/50xxx/CVE-2026-50735.json">CVE-2026-50735</a>
      Referenceadded
      —
      https://github.com/pgEdge/spock/security/advisories/GHSA-j2m3-f88h-2h46
      Referenceadded
      —
      https://www.enterprisedb.com/docs/security/advisories/cve202650735/
      Referenceremoved
      https://www.enterprisedb.com/docs/security/advisories/cve202650735/
      —
      Reference typeremoved
      https://www.enterprisedb.com/docs/security/advisories/cve202650735/ Types: Vendor Advisory
      —

      Source identifier: 20be33e2-bf35-4d13-8fad-18bd2f3e3659

    2. Initial analysis by NVDNVD

      Newly listed as affected:

      CVSS V3.1: AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H

      Show 3 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      CVSSadded
      —
      AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H
      Product configurationadded
      —
      OR *cpe:2.3:a:enterprisedb:pglogical:*:*:*:*:*:postgresql:*:* versions from (including) 2.0.0 up to (excluding) 2.4.8
      Reference typeadded
      —
      EnterpriseDB Corporation: https://www.enterprisedb.com/docs/security/advisories/cve202650735/ Types: Vendor Advisory

      Source identifier: nvd@nist.gov

    3. Received20be33e2…

      CVSS V4.0: AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N

      Weakness type: CWE-125

      Description added or changed

      Show 5 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Affected versions (publisher)added
      —
      pglogical
      Descriptionadded
      —
      pglogical's apply worker does not sufficiently validate the length of certain fields in incoming replication protocol messages before copying them, resulting in an out-of-bounds read. A party acting as the publisher for a subscription, for example a non-PostgreSQL endpoint that speaks the pglogical replication protocol, can return crafted messages that cause the subscriber's apply worker to read beyond the bounds of an allocated buffer, disclosing adjacent process memory or crashing the worker. To exploit the issue an attacker must be able to direct a subscription at an endpoint they control. In default installations this requires privileges normally reserved for a superuser, so the issue is most relevant to managed deployments where the ability to create subscriptions has been delegated to non-superuser roles.
      CVSSadded
      —
      AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
      Weakness type (CWE)added
      —
      CWE-125
      Referenceadded
      —
      https://www.enterprisedb.com/docs/security/advisories/cve202650735/

      Source identifier: 20be33e2-bf35-4d13-8fad-18bd2f3e3659

    One NVD translation into another language is hidden.

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-50735
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-50735"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-50735.svg?lang=en" alt="CVE-2026-50735 – NEOSEC Intel" height="20"></a>