CVE-2026-61817

HIGHPre-NVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 48% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

pg_partman is a PostgreSQL extension that manages partitioned tables by time or ID. Prior to 5.5.0, run_maintenance(), show_partitions(), show_partition_info(), undo_partition(), and partition_data_time() interpolate the writable part_config.time_dncoder text value without identifier quoting into dynamic SQL. A role with the documented partman_user privileges can store SQL rather than a decoder function name. When an affected operation later uses the poisoned value, including pg_partman_bgw maintenance for a text- or UUID-keyed set, the SQL executes with the operation's privileges, which can be the default PostgreSQL superuser background-worker role. The persistent row can restore elevated access on later ticks, and successful exploitation can permit database-wide compromise and operating-system command execution as the PostgreSQL service account. This issue is fixed in version 5.5.0.

CVSS v3
8.5
EG Score
8.5(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity85% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

September 18, 2026

Last Modified

September 24, 2026

Advisory Details (2)

Auto-updated Sep 18, 2026
Patch available. Sources: github_release, github.
github_release Patch Available

v5.5.0

Patch available: pgpartman/pg_partman v5.5.0

https://github.com/pgpartman/pg_partman/releases/tag/v5.5.0
github Patch Available

pg_partman privilege escalation via SQL injection in several functions via time decoder · Advisory · pgpartman/pg_partman · GitHub

https://github.com/pgpartman/pg_partman/security/advisories/GHSA-gmw2-52wc-258g

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 21:38 UTCEG score recompute
  2. 2026-09-23 23:09 UTCEG score recompute
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 23:55 UTCEG score recompute
  5. 2026-09-22 00:56 UTCEG score recompute
  6. 2026-09-21 01:57 UTCEG score recompute
  7. 2026-09-20 20:16 UTCEPSS rescore
  8. 2026-09-20 02:58 UTCEG score recompute
  9. 2026-09-19 15:28 UTCEG score recompute
  10. 2026-09-19 14:25 UTCEG score recompute
  11. 2026-09-18 20:30 UTCEG score recompute
  12. 2026-09-18 19:54 UTCEG score recompute
  13. 2026-09-18 19:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61817?
CVE-2026-61817 is a high vulnerability published on September 18, 2026. pgpartman is a PostgreSQL extension that manages partitioned tables by time or ID. Prior to 5.5.0, runmaintenance(), showpartitions(), showpartitioninfo(), undopartition(), and partitiondatatime() interpolate the writable partconfig.timedncoder text value without identifier quoting into dynamic…
When was CVE-2026-61817 disclosed?
CVE-2026-61817 was first published in the National Vulnerability Database on September 18, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61817 actively exploited?
CVE-2026-61817 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.8% of all scored CVEs.
What is the CVSS score of CVE-2026-61817?
CVE-2026-61817 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-61817?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61817, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-61817

Explore →

Is Your Infrastructure Affected by CVE-2026-61817?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs