{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-61820 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-61820 is a high-severity SQL injection vulnerability in pgpartman pg_partman, published on 18 Sep 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-61820 and fix it if it is affected.\n\nWhat it is: CVE-2026-61820 is a high-severity SQL injection vulnerability in pgpartman pg_partman, published on 18 Sep 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-61820 in the wild and no public exploit code.\n\nAffected product: pgpartman pg_partman. 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-61820/ (Markdown: https://insights.sbomify.com/CVE-2026-61820/index.md)","id":"CVE-2026-61820","markdown":"https://insights.sbomify.com/CVE-2026-61820/index.md","name":"CVE-2026-61820","record":{"aliases":["DEBIAN-CVE-2026-61820","ECHO-18af-f647-c2f7","GHSA-xqxh-6hh3-974m","UBUNTU-CVE-2026-61820"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"PostgreSQL extension","requires_auth":"low_privilege","summary":"A SQL injection in pg_partman allows a partman_user to execute arbitrary SQL as superuser via crafted column names, leading to full database and OS compromise.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"pg_partman is a PostgreSQL extension that manages partitioned tables by time or ID. Prior to 5.5.0, inherit_template_properties() manually surrounds primary-key column names from pg_attribute.attname with double quotes without escaping embedded double-quote characters. A partman_user who owns a template table can create a crafted column name that breaks out of the generated ALTER TABLE ADD PRIMARY KEY identifier when the background worker applies the key to a child partition. The generated SQL then executes with pg_partman_bgw.role privileges, which default to PostgreSQL superuser, permitting database-wide compromise and operating-system command execution as the PostgreSQL service account. The crafted catalog identifier persists until removed and can trigger again during later partition creation. This issue is fixed in version 5.5.0.","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":"pg_partman privilege escalation via SQL injection when inheriting template properties","id":"CVE-2026-61820","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"pg_partman authorization bypass to move child tables between schemas during retention","id":"CVE-2026-61821"},"packages":[],"prev":{"headline":"pg_partman privilege escalation via SQL injection in when using pg_jobmon and encountering exception","id":"CVE-2026-61819"},"products":["pg_partman"],"published":"2026-09-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-22","vendors":["pgpartman"]},"summary":"A SQL injection in pg_partman allows a partman_user to execute arbitrary SQL as superuser via crafted column names, leading to full database and OS compromise.","url":"https://insights.sbomify.com/CVE-2026-61820/"}