{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-50736 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-50736 is a critical SQL injection 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-50736 and fix it if it is affected.\n\nWhat it is: CVE-2026-50736 is a critical SQL injection 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-50736 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-50736/ (Markdown: https://insights.sbomify.com/CVE-2026-50736/index.md)","id":"CVE-2026-50736","markdown":"https://insights.sbomify.com/CVE-2026-50736/index.md","name":"CVE-2026-50736","record":{"aliases":["DEBIAN-CVE-2026-50736","ECHO-f126-0745-5489","GHSA-cg29-63x4-27px","UBUNTU-CVE-2026-50736"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"PostgreSQL extension","requires_auth":"low_privilege","summary":"A malicious publisher can execute arbitrary SQL as superuser on a subscriber via crafted queue messages, requiring delegated subscription creation privileges.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EDB","cpe":[{"product":"pglogical","vendor":"enterprisedb"}],"cvss":{"score":9,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The pglogical queue mechanism, used to convey out-of-band commands such as replicated DDL from a publisher to a subscriber, executes message payloads on the subscriber at the privilege level of the apply worker, which is equivalent to a PostgreSQL superuser in default installations. A party acting as the publisher can send crafted queue messages that cause arbitrary SQL to be executed on the subscriber as superuser, escalating from a role permitted to use pglogical to full superuser and breaking the isolation between tenants in shared deployments. 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":"SQL injection in pglogical","id":"CVE-2026-50736","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in pglogical","id":"CVE-2026-50737"},"packages":[],"prev":{"headline":"Information disclosure in pglogical","id":"CVE-2026-50735"},"products":["pglogical"],"published":"2026-07-28","related":[{"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"},{"cvss_score":6.1,"headline":"Information disclosure in pglogical","id":"CVE-2026-50735","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":"total"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["EnterpriseDB"]},"summary":"A malicious publisher can execute arbitrary SQL as superuser on a subscriber via crafted queue messages, requiring delegated subscription creation privileges.","url":"https://insights.sbomify.com/CVE-2026-50736/"}