{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-50735 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-50735 is a medium-severity vulnerability in EnterpriseDB pglogical, published on 28 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-50735 and fix it if it is affected.\n\nWhat it is: CVE-2026-50735 is a medium-severity vulnerability in EnterpriseDB pglogical, published on 28 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-50735 in the wild and no public exploit code.\n\nAffected product: EnterpriseDB pglogical. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-50735/ (Markdown: https://insights.sbomify.com/CVE-2026-50735/index.md)","id":"CVE-2026-50735","markdown":"https://insights.sbomify.com/CVE-2026-50735/index.md","name":"CVE-2026-50735","record":{"aliases":["DEBIAN-CVE-2026-50735","ECHO-adab-4650-fa5e","GHSA-jhwv-w4qj-9cmf","UBUNTU-CVE-2026-50735"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"PostgreSQL logical replication","requires_auth":"low_privilege","summary":"A malicious publisher can cause out-of-bounds reads in pglogical subscribers, leaking memory or crashing workers, primarily affecting managed deployments with delegated subscription privileges.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EDB","cpe":[{"product":"pglogical","vendor":"enterprisedb"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in pglogical","id":"CVE-2026-50735","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in pglogical","id":"CVE-2026-50736"},"packages":[],"prev":{"headline":"Denial of service in Apache ActiveMQ","id":"CVE-2026-50734"},"products":["pglogical"],"published":"2026-07-28","related":[{"cvss_score":9,"headline":"SQL injection in pglogical","id":"CVE-2026-50736","kev_date_added":null,"published":"2026-07-28"},{"cvss_score":9,"headline":"Privilege escalation in pglogical","id":"CVE-2026-50737","kev_date_added":null,"published":"2026-07-28"},{"cvss_score":7.7,"headline":"Use after free in pglogical","id":"CVE-2026-50738","kev_date_added":null,"published":"2026-07-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["EnterpriseDB"]},"summary":"A malicious publisher can cause out-of-bounds reads in pglogical subscribers, leaking memory or crashing workers, primarily affecting managed deployments with delegated subscription privileges.","url":"https://insights.sbomify.com/CVE-2026-50735/"}