CVE-2026-61781

CRITICALPre-NVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 45% 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
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.9Exploit: 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, create_partition_time() reads the writable part_config.time_encoder text value and interpolates it without identifier quoting into a dynamically executed SELECT statement. A role with the documented partman_user INSERT and UPDATE privileges can store SQL rather than a function name. When pg_partman_bgw later creates a child partition for a text- or UUID-keyed set, the worker executes the stored SQL with pg_partman_bgw.role privileges, which default to PostgreSQL superuser. The persistent configuration row can repeatedly restore elevated access on later maintenance 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
9.9
EG Score
9.9(medium)
EG Risk
45(Track)
EG Risk 45/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
Severity99% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
55%
KEV
Not listed

Published

September 18, 2026

Last Modified

September 23, 2026

Advisory Details (2)

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

pg_partman privilege escalation via SQL injection in create_partition_time time encoder · Advisory · pgpartman/pg_partman · GitHub

https://github.com/pgpartman/pg_partman/security/advisories/GHSA-742w-3j7c-qwvp
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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 11× 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 16:01 UTCEG score recompute
  2. 2026-09-23 18:27 UTCEG score recompute
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 18:15 UTCEG score recompute
  5. 2026-09-21 21:09 UTCEG score recompute
  6. 2026-09-20 23:56 UTCEG score recompute
  7. 2026-09-20 20:16 UTCEPSS rescore
  8. 2026-09-19 18:22 UTCEG score recompute
  9. 2026-09-18 20:29 UTCEG score recompute
  10. 2026-09-18 19:49 UTCEG score recompute
  11. 2026-09-18 19:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-61781?
CVE-2026-61781 is a critical vulnerability published on September 18, 2026. pgpartman is a PostgreSQL extension that manages partitioned tables by time or ID. Prior to 5.5.0, createpartitiontime() reads the writable partconfig.timeencoder text value and interpolates it without identifier quoting into a dynamically executed SELECT statement. A role with the documented…
When was CVE-2026-61781 disclosed?
CVE-2026-61781 was first published in the National Vulnerability Database on September 18, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61781 actively exploited?
CVE-2026-61781 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 45.2% of all scored CVEs.
What is the CVSS score of CVE-2026-61781?
CVE-2026-61781 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-61781?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61781, 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-61781

Explore →

Is Your Infrastructure Affected by CVE-2026-61781?

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