CVE-2024-9014

CRITICALNVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 9.7%, top 5% 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, nvd
Elevated
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 10%CVSS: 9.9Exploit: Elevated riskExposed: 0

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

pgAdmin versions 8.11 and earlier are vulnerable to a security flaw in OAuth2 authentication. This vulnerability allows an attacker to potentially obtain the client ID and secret, leading to unauthorized access to user data.

CVSS v3
9.9
EG Score
9.9(medium)
EG Risk
61(Track)
EG Risk 61/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%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
10%
EPSS %ILE
95%
KEV
Not listed

Published

September 23, 2024

Last Modified

September 22, 2025

Advisory Details (1)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

OAuth2 issue in pgAdmin 4. · Issue #7945 · pgadmin-org/pgadmin4 · GitHub

https://github.com/pgadmin-org/pgadmin4/issues/7945

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
pgadmin44.20 ... 8.9 (59 versions)8.12—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 41× 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-07-27 14:12 UTCEPSS rescore
  2. 2026-07-25 14:17 UTCEPSS rescore
  3. 2026-07-25 14:17 UTCEPSS rescore
  4. 2026-07-23 14:17 UTCEPSS rescore
  5. 2026-07-23 02:46 UTCEG score recompute
  6. 2026-07-22 14:07 UTCEPSS rescore
  7. 2026-07-22 14:07 UTCEPSS rescore
  8. 2026-07-21 15:24 UTCEPSS rescore
  9. 2026-07-20 17:07 UTCEPSS rescore
  10. 2026-07-19 14:30 UTCEPSS rescore
  11. 2026-07-19 02:28 UTCEPSS rescore
  12. 2026-07-19 02:28 UTCEPSS rescore
  13. 2026-07-18 10:03 UTCEPSS rescore
  14. 2026-07-18 10:03 UTCEPSS rescore
  15. 2026-07-16 17:02 UTCEPSS rescore
  16. 2026-07-16 17:02 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 16:57 UTCEPSS rescore
  19. 2026-07-15 01:59 UTCEPSS rescore
  20. 2026-07-15 01:59 UTCEPSS rescore
  21. 2026-07-14 01:00 UTCOSV refresh
  22. 2026-07-13 22:29 UTCEPSS rescore
  23. 2026-07-13 22:29 UTCEPSS rescore
  24. 2026-07-12 05:45 UTCEPSS rescore
  25. 2026-07-12 05:45 UTCEPSS rescore
Show 57 more
  1. 2026-07-11 08:26 UTCEPSS rescore
  2. 2026-07-09 19:09 UTCEPSS rescore
  3. 2026-07-09 19:09 UTCEPSS rescore
  4. 2026-07-08 15:14 UTCEPSS rescore
  5. 2026-07-07 13:45 UTCEPSS rescore
  6. 2026-07-06 16:26 UTCEPSS rescore
  7. 2026-07-06 16:26 UTCEPSS rescore
  8. 2026-07-06 02:22 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 06:30 UTCEPSS rescore
  11. 2026-07-04 06:30 UTCEPSS rescore
  12. 2026-07-02 17:00 UTCEPSS rescore
  13. 2026-07-01 15:06 UTCEPSS rescore
  14. 2026-06-30 23:21 UTCEPSS rescore
  15. 2026-06-28 04:55 UTCEPSS rescore
  16. 2026-06-28 04:55 UTCEPSS rescore
  17. 2026-06-27 03:08 UTCEPSS rescore
  18. 2026-06-25 22:46 UTCOSV refresh
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 14:04 UTCEPSS rescore
  22. 2026-06-23 21:32 UTCEPSS rescore
  23. 2026-06-23 21:32 UTCEPSS rescore
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-22 14:25 UTCEPSS rescore
  26. 2026-06-21 14:56 UTCEPSS rescore
  27. 2026-06-21 14:56 UTCEPSS rescore
  28. 2026-06-21 01:59 UTCEPSS rescore
  29. 2026-06-19 19:25 UTCEPSS rescore
  30. 2026-06-19 19:25 UTCEPSS rescore
  31. 2026-06-18 17:52 UTCEPSS rescore
  32. 2026-06-18 17:52 UTCEPSS rescore
  33. 2026-06-17 17:52 UTCEPSS rescore
  34. 2026-06-16 17:52 UTCEPSS rescore
  35. 2026-06-15 17:48 UTCEPSS rescore
  36. 2026-06-15 17:48 UTCEPSS rescore
  37. 2026-06-13 22:59 UTCEPSS rescore
  38. 2026-06-11 13:59 UTCEPSS rescore
  39. 2026-06-10 22:18 UTCEPSS rescore
  40. 2026-06-10 22:18 UTCEPSS rescore
  41. 2026-06-08 14:16 UTCEPSS rescore
  42. 2026-06-08 14:16 UTCEPSS rescore
  43. 2026-06-08 12:06 UTCOSV refresh
  44. 2026-05-31 00:16 UTCEPSS rescore
  45. 2026-05-31 00:16 UTCEPSS rescore
  46. 2026-05-29 13:43 UTCEPSS rescore
  47. 2026-05-28 13:44 UTCEPSS rescore
  48. 2026-05-28 13:44 UTCEPSS rescore
  49. 2026-05-28 13:44 UTCEPSS rescore
  50. 2026-05-27 13:40 UTCEPSS rescore
  51. 2026-05-27 13:40 UTCEPSS rescore
  52. 2026-05-27 13:40 UTCEPSS rescore
  53. 2026-05-26 07:18 UTCEPSS rescore
  54. 2026-05-26 07:18 UTCEPSS rescore
  55. 2026-05-26 07:18 UTCEPSS rescore
  56. 2026-05-26 07:18 UTCEPSS rescore
  57. 2026-05-23 21:43 UTCEG score recompute

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCEQSTLab/CVE-2024-9014
    First seen Sep 26, 2024

    Pgadmin4 Sensitive Information Exposure

    Open source ↗
  • Nucleihttp/cves/2024/CVE-2024-9014.yaml
    First seen Jan 1, 2024

    pgAdmin 4 - Authentication Bypass

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-9014?
CVE-2024-9014 is a critical vulnerability published on September 23, 2024. pgAdmin versions 8.11 and earlier are vulnerable to a security flaw in OAuth2 authentication. This vulnerability allows an attacker to potentially obtain the client ID and secret, leading to unauthorized access to user data.
When was CVE-2024-9014 disclosed?
CVE-2024-9014 was first published in the National Vulnerability Database on September 23, 2024, with the most recent update on September 22, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-9014 actively exploited?
CVE-2024-9014 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10% probability of exploitation in the next 30 days, which ranks it in the top 5.0% of all scored CVEs.
What is the CVSS score of CVE-2024-9014?
CVE-2024-9014 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2024-9014?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-9014, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2024-9014?

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

Start Free Scan →Browse All CVEs