CVE-2026-61820

HIGHPre-NVD 8.58.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (54th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-83433 (ENISA EUVD)Source: ENISA EUVD

8.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity85% × 45%
Impact severity (EG Severity): CVSS 8.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
54th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.5): severity, escalated by confirmed exploitation. This CVE's 8.5 is its impact severity (EG Severity), not escalated.

EG Severity
8.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 18, 2026

Last Modified

September 23, 2026

Advisory Details (2)

Auto-updated Sep 18, 2026
Patch available. Sources: github, github_release.
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 advisoryMentions a patch (unverified)

pg_partman privilege escalation via SQL injection when inheriting template properties · Advisory · pgpartman/pg_partman · GitHub

https://github.com/pgpartman/pg_partman/security/advisories/GHSA-xqxh-6hh3-974m

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
pg-partman4.7.2-1 ... 5.5.0-1 (21 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pg-partman5.2.4-1 ... 5.5.0-1 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pg-partman5.2.4-1 ... 5.4.3-1 (9 versions)
  • every version up to 5.5.0-1: fixed in 5.5.0-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  3. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  5. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  6. 2026-10-28 05:51 UTCEG score recompute
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-10-25 14:14 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  15. 2026-10-20 18:53 UTCEG score recompute
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  18. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  19. 2026-10-18 03:25 UTCEG score recompute
  20. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  21. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  22. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  23. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  24. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-10-13 13:20 UTCEG score recompute
Show 48 more
  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-10-12 15:50 UTCEG score recompute
  3. 2026-10-11 19:34 UTCEG score recompute
  4. 2026-10-11 16:49 UTCEG score recompute
  5. 2026-10-11 14:11 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-10-11 05:53 UTCEG score recompute
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  9. 2026-10-10 06:47 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-10-08 20:14 UTCEG score recompute
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-08 07:29 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-10-06 20:45 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-10-05 21:45 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-10-05 09:52 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-10-03 23:21 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-10-02 23:50 UTCEG score recompute
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-10-02 00:07 UTCEG score recompute
  26. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  27. 2026-10-01 00:22 UTCEG score recompute
  28. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  29. 2026-09-30 00:56 UTCEG score recompute
  30. 2026-09-29 01:52 UTCEG score recompute
  31. 2026-09-28 14:22 UTCEG score recompute
  32. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  33. 2026-09-27 15:20 UTCEG score recompute
  34. 2026-09-26 16:13 UTCEG score recompute
  35. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  36. 2026-09-26 04:40 UTCEG score recompute
  37. 2026-09-24 18:01 UTCEG score recompute
  38. 2026-09-23 18:40 UTCEG score recompute
  39. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  40. 2026-09-22 16:23 UTCEG score recompute
  41. 2026-09-22 15:46 UTCEG score recompute
  42. 2026-09-22 05:04 UTCEG score recompute
  43. 2026-09-21 06:02 UTCEG score recompute
  44. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  45. 2026-09-19 19:31 UTCEG score recompute
  46. 2026-09-18 20:30 UTCEG score recompute
  47. 2026-09-18 19:54 UTCEG score recomputeFirst assessed: 8.5 HIGH
  48. 2026-09-18 19:54 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-61820?
CVE-2026-61820 is a high-severity vulnerability; its CVE record was published on September 18, 2026. 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…
When was the CVE record for CVE-2026-61820 published?
The CVE record for CVE-2026-61820 was published on September 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 23, 2026; the record at its source may have been updated since.
Is CVE-2026-61820 actively exploited?
CVE-2026-61820 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61820?
CVE-2026-61820 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61820?
A fix for CVE-2026-61820 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61820

Explore →

Is Your Infrastructure Affected by CVE-2026-61820?

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

Book a Demo →Browse All CVEs