CVE-2024-10978

MEDIUMNVD 4.24.2
EchelonGraph scoreMEDIUM confidence

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

Score 4.2 from GitHub Security Advisory (severity: MODERATE) published 2024-11-14. NVD baseline CVSS 4.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-33376 (ENISA EUVD) · GHSA-37v9-jh5m-f5pg (GitHub Security Advisories)Source: ENISA EUVD

4.2EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 4.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature. The problem arises when an application query uses parameters from the attacker or conveys query results to the attacker. If that query reacts to current_setting('role') or the current user ID, it may modify or return data as though the session had not used SET ROLE or SET SESSION AUTHORIZATION. The attacker does not control which incorrect user ID applies. Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION AUTHORIZATION are not sandboxes for unvetted queries. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.

CVSS v3
4.2
EG Score
4.2MEDIUMmedium confidence
EG Risk
19
EG Risk 19/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)
Severity42% × 45%
Impact severity (EG Severity): CVSS 4.2 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
53rd
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 (4.2): severity, escalated by confirmed exploitation. This CVE's 4.2 is its impact severity (EG Severity), not escalated.

EG Severity
4.2 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

November 14, 2024

Last Modified

November 3, 2025

References (4)

Vendor Advisories for CVE-2024-10978(8)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupostgresql-server-dev-12 (12.22-0ubuntu0.20.04.1) @ focal2026-10-24ubuntu
ubuntupostgresql-server-dev-9.5 (9.5.25-0ubuntu0.16.04.1+esm10) @ xenial2026-10-24ubuntu
redhatpostgresql:15-8100020241122084744.489197e62024-12-05redhat
redhatpostgresql:16-8100020241122085009.489197e62024-12-05redhat
redhatpostgresql:13-8100020241122084628.489197e62024-12-05redhat
redhatpostgresql:15-9050020241122141928.rhel92024-12-04redhat
redhatpostgresql:16-9050020241122142517.rhel92024-12-04redhat
redhatpostgresql-0:13.18-1.el9_52024-12-04redhat
redhatpostgresql:12-8100020241122084405.489197e62024-12-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(26 across 11 ecosystems)
Alpine:v3.19(4)
PackageVulnerable rangeFix by version rangeDependents
postgresql13—
  • every version up to 13.17-r0: fixed in 13.17-r0
—
postgresql14—
  • every version up to 14.14-r0: fixed in 14.14-r0
—
postgresql15—
  • every version up to 15.9-r0: fixed in 15.9-r0
—
postgresql16—
  • every version up to 16.5-r0: fixed in 16.5-r0
—
Alpine:v3.17(3)
PackageVulnerable rangeFix by version rangeDependents
postgresql13—
  • every version up to 13.17-r0: fixed in 13.17-r0
—
postgresql14—
  • every version up to 14.14-r0: fixed in 14.14-r0
—
postgresql15—
  • every version up to 15.9-r0: fixed in 15.9-r0
—
Alpine:v3.18(3)
PackageVulnerable rangeFix by version rangeDependents
postgresql13—
  • every version up to 13.17-r0: fixed in 13.17-r0
—
postgresql14—
  • every version up to 14.14-r0: fixed in 14.14-r0
—
postgresql15—
  • every version up to 15.9-r0: fixed in 15.9-r0
—
Alpine:v3.20(3)
PackageVulnerable rangeFix by version rangeDependents
postgresql14—
  • every version up to 14.14-r0: fixed in 14.14-r0
—
postgresql15—
  • every version up to 15.9-r0: fixed in 15.9-r0
—
postgresql16—
  • every version up to 16.5-r0: fixed in 16.5-r0
—
Alpine:v3.21(3)
PackageVulnerable rangeFix by version rangeDependents
postgresql15—
  • every version up to 15.9-r0: fixed in 15.9-r0
—
postgresql16—
  • every version up to 16.5-r0: fixed in 16.5-r0
—
postgresql17—
  • every version up to 17.1-r0: fixed in 17.1-r0
—
Alpine:v3.22(3)
PackageVulnerable rangeFix by version rangeDependents
postgresql15—
  • every version up to 15.9-r0: fixed in 15.9-r0
—
postgresql16—
  • every version up to 16.5-r0: fixed in 16.5-r0
—
postgresql17—
  • every version up to 17.1-r0: fixed in 17.1-r0
—
Alpine:v3.23(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql16—
  • every version up to 16.5-r0: fixed in 16.5-r0
—
postgresql17—
  • every version up to 17.1-r0: fixed in 17.1-r0
—
Alpine:v3.24(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql16—
  • every version up to 16.5-r0: fixed in 16.5-r0
—
postgresql17—
  • every version up to 17.1-r0: fixed in 17.1-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1313.10-0+deb11u1 ... 13.9-0+deb11u1 (16 versions)
  • every version up to 13.17-0+deb11u1: fixed in 13.17-0+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1515.3-0+deb12u1 ... 15.8-0+deb12u1 (10 versions)
  • every version up to 15.9-0+deb12u1: fixed in 15.9-0+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-17—
  • every version up to 17.1-1: fixed in 17.1-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 33× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 234 rows on record for this CVE, as 96 entries (4 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 134 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:46 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-11-12 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  3. 2026-11-11 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-11-10 16:38 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-11-09 16:30 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-11-08 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  7. 2026-11-07 21:14 UTCGHSA enrichmentGHSA-37v9-jh5m-f5pg · GitHub severity MODERATE · GitHub CVSS 4.2
  8. 2026-11-07 21:14 UTCEchelonGraph re-scored
  9. 2026-11-07 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-11-05 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  12. 2026-11-04 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-11-03 16:41 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  20. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  21. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  22. 2026-10-25 17:23 UTCEchelonGraph re-scored
  23. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  25. 2026-10-24 09:52 UTCEchelonGraph re-scored
Show 71 more
  1. 2026-10-24 09:52 UTCVendor advisory
  2. 2026-10-24 09:52 UTCGHSA enrichmentGHSA-37v9-jh5m-f5pg · GitHub CVSS 4.2
  3. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  4. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  5. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  6. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  7. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  8. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  9. 2026-10-18 07:35 UTCEchelonGraph re-scored
  10. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  11. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  12. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  13. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  14. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  15. 2026-10-12 18:08 UTCEchelonGraph re-scored
  16. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  17. 2026-10-11 21:33 UTCEchelonGraph re-scored
  18. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  19. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  20. 2026-10-10 08:55 UTCOSV refresh
  21. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  22. 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  23. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  24. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  26. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  27. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  28. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  29. 2026-09-30 16:42 UTCEchelonGraph re-scored
  30. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  31. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  32. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  33. 2026-09-27 13:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  34. 2026-09-26 00:23 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  35. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  36. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  37. 2026-09-22 14:46 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  38. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  39. 2026-09-20 18:14 UTCOSV refresh
  40. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  41. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  42. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  43. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  44. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  45. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  46. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  47. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  48. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  49. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  50. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  51. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  52. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  53. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  54. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  55. 2026-09-01 18:26 UTCOSV refresh
  56. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  57. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  58. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  59. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  60. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  61. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  62. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  63. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  64. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  65. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  66. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  67. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  68. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  69. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  70. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  71. 2026-08-15 19:37 UTCOSV refresh

Related CVEs(same product + same vendor + same CWE)

Same vendor

3 shown

redhat:RHSA-2024:10785 · ubuntu:USN-7132-1

Frequently asked(5)

What is CVE-2024-10978?
CVE-2024-10978 is a medium-severity vulnerability; its CVE record was published on November 14, 2024. Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature. The problem arises when an application query uses…
When was the CVE record for CVE-2024-10978 published?
The CVE record for CVE-2024-10978 was published on November 14, 2024. 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 November 3, 2025; the record at its source may have been updated since.
Is CVE-2024-10978 actively exploited?
CVE-2024-10978 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-10978?
CVE-2024-10978 has a CVSS v3 base score of 4.2 (NVD).
How do I remediate CVE-2024-10978?
A fix for CVE-2024-10978 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-10978 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-10978

Explore →

Is Your Infrastructure Affected by CVE-2024-10978?

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

Book a Demo →Browse All CVEs