CVE-2019-12838

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-24. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3%CVSS: 9.8Exploit: None knownExposed: 0

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

SchedMD Slurm 17.11.x, 18.08.0 through 18.08.7, and 19.05.0 allows SQL Injection.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
50(Track)
EG Risk 50/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
Severity98% × 45%
Exploitation3% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
3%
EPSS %ILE
85%
KEV
Not listed

Published

July 11, 2019

Last Modified

November 21, 2024

Advisory Details (7)

Auto-updated Aug 16, 2026
Patch available.
generic

Bugtraq: [SECURITY] [DSA 4572-1] slurm-llnl security update

https://seclists.org/bugtraq/2019/Nov/30
generic

[slurm-announce] Slurm versions 19.05.1 and 18.08.8 are now available (CVE-2019-12838)

https://lists.schedmd.com/pipermail/slurm-announce/2019/000025.html
generic

The slurm-announce 2019 Archive by thread

https://lists.schedmd.com/pipermail/slurm-announce/2019/
generic

[SECURITY] Fedora 30 Update: slurm-18.08.8-1.fc30 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/AQ6EV3OWKGMTBWCSXZGS4MYADUBLVXSQ/
generic

[SECURITY] Fedora 29 Update: slurm-18.08.8-1.fc29 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/2O47F72FWMYLEGF35QGNYY5VS33SUQS5/
generic Patch Available

[SECURITY] [DLA 2886-1] slurm-llnl security update

https://lists.debian.org/debian-lts-announce/2022/01/msg00011.html
generic Patch Available

[SECURITY] [DLA 2143-1] slurm-llnl security update

https://lists.debian.org/debian-lts-announce/2020/03/msg00016.html

Affected Packages

(3 across 3 ecosystems)
Debian:10(1)
PackageVulnerable rangeFixed inDependents
slurm-llnl18.08.5.2-118.08.5.2-1+deb10u1—
Debian:8(1)
PackageVulnerable rangeFixed inDependents
slurm-llnl14.03.9-5, 14.03.9-5+deb8u1, 14.03.9-5+deb8u2, 14.03.9-5+deb8u3, 14.03.9-5+deb8u414.03.9-5+deb8u5—
Debian:9(1)
PackageVulnerable rangeFixed inDependents
slurm-llnl16.05.9-1, 16.05.9-1+deb9u1, 16.05.9-1+deb9u2, 16.05.9-1+deb9u3, 16.05.9-1+deb9u416.05.9-1+deb9u5—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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.

Showing the most recent 100 of 122 total refreshes for this CVE.

  1. 2026-08-21 19:14 UTCOSV refresh
  2. 2026-08-20 22:51 UTCEPSS rescore
  3. 2026-08-19 17:00 UTCEPSS rescore
  4. 2026-08-18 13:44 UTCEPSS rescore
  5. 2026-08-17 13:43 UTCEPSS rescore
  6. 2026-08-16 14:52 UTCEPSS rescore
  7. 2026-08-16 02:10 UTCEPSS rescore
  8. 2026-08-15 01:26 UTCEPSS rescore
  9. 2026-08-13 21:56 UTCEPSS rescore
  10. 2026-08-12 13:47 UTCEPSS rescore
  11. 2026-08-09 13:43 UTCEPSS rescore
  12. 2026-08-08 16:33 UTCEPSS rescore
  13. 2026-08-07 16:23 UTCEPSS rescore
  14. 2026-08-06 13:43 UTCEPSS rescore
  15. 2026-08-06 02:54 UTCOSV refresh
  16. 2026-08-05 19:13 UTCEPSS rescore
  17. 2026-08-04 15:05 UTCEPSS rescore
  18. 2026-08-04 10:33 UTCEPSS rescore
  19. 2026-08-03 10:31 UTCEPSS rescore
  20. 2026-08-02 02:23 UTCEPSS rescore
  21. 2026-08-01 04:12 UTCEPSS rescore
  22. 2026-07-30 16:24 UTCEPSS rescore
  23. 2026-07-30 01:27 UTCEPSS rescore
  24. 2026-07-28 15:32 UTCEPSS rescore
  25. 2026-07-26 14:51 UTCEPSS rescore
Show 75 more
  1. 2026-07-25 14:14 UTCEPSS rescore
  2. 2026-07-24 14:14 UTCEPSS rescore
  3. 2026-07-24 14:14 UTCEPSS rescore
  4. 2026-07-23 14:15 UTCEPSS rescore
  5. 2026-07-23 01:39 UTCEG score recompute
  6. 2026-07-22 22:19 UTCEG score recompute
  7. 2026-07-22 14:05 UTCEPSS rescore
  8. 2026-07-21 15:22 UTCEPSS rescore
  9. 2026-07-21 15:22 UTCEPSS rescore
  10. 2026-07-20 17:04 UTCEPSS rescore
  11. 2026-07-20 13:02 UTCOSV refresh
  12. 2026-07-19 14:28 UTCEPSS rescore
  13. 2026-07-19 14:28 UTCEPSS rescore
  14. 2026-07-19 02:26 UTCEPSS rescore
  15. 2026-07-19 02:26 UTCEPSS rescore
  16. 2026-07-18 10:01 UTCEPSS rescore
  17. 2026-07-16 16:59 UTCEPSS rescore
  18. 2026-07-16 16:59 UTCEPSS rescore
  19. 2026-07-15 16:55 UTCEPSS rescore
  20. 2026-07-13 22:27 UTCEPSS rescore
  21. 2026-07-13 06:10 UTCEPSS rescore
  22. 2026-07-13 06:10 UTCEPSS rescore
  23. 2026-07-12 05:43 UTCEPSS rescore
  24. 2026-07-11 08:24 UTCEPSS rescore
  25. 2026-07-09 19:06 UTCEPSS rescore
  26. 2026-07-08 15:11 UTCEPSS rescore
  27. 2026-07-07 13:42 UTCEPSS rescore
  28. 2026-07-06 16:25 UTCEPSS rescore
  29. 2026-07-06 02:20 UTCEPSS rescore
  30. 2026-07-05 02:27 UTCEPSS rescore
  31. 2026-07-04 06:28 UTCEPSS rescore
  32. 2026-07-04 06:28 UTCEPSS rescore
  33. 2026-07-03 08:26 UTCOSV refresh
  34. 2026-07-02 16:56 UTCEPSS rescore
  35. 2026-07-01 15:03 UTCEPSS rescore
  36. 2026-07-01 15:03 UTCEPSS rescore
  37. 2026-06-30 23:20 UTCEPSS rescore
  38. 2026-06-30 23:20 UTCEPSS rescore
  39. 2026-06-29 14:03 UTCEPSS rescore
  40. 2026-06-28 14:04 UTCEPSS rescore
  41. 2026-06-28 04:54 UTCEPSS rescore
  42. 2026-06-28 04:53 UTCEPSS rescore
  43. 2026-06-27 03:06 UTCEPSS rescore
  44. 2026-06-27 03:06 UTCEPSS rescore
  45. 2026-06-25 13:47 UTCEPSS rescore
  46. 2026-06-25 13:47 UTCEPSS rescore
  47. 2026-06-24 14:03 UTCEPSS rescore
  48. 2026-06-24 14:02 UTCEPSS rescore
  49. 2026-06-23 21:30 UTCEPSS rescore
  50. 2026-06-23 21:30 UTCEPSS rescore
  51. 2026-06-22 14:23 UTCEPSS rescore
  52. 2026-06-22 14:23 UTCEPSS rescore
  53. 2026-06-21 14:54 UTCEPSS rescore
  54. 2026-06-21 14:54 UTCEPSS rescore
  55. 2026-06-21 01:57 UTCEPSS rescore
  56. 2026-06-21 01:57 UTCEPSS rescore
  57. 2026-06-19 19:23 UTCEPSS rescore
  58. 2026-06-19 19:23 UTCEPSS rescore
  59. 2026-06-18 17:50 UTCEPSS rescore
  60. 2026-06-17 17:50 UTCEPSS rescore
  61. 2026-06-16 17:50 UTCEPSS rescore
  62. 2026-06-15 17:45 UTCEPSS rescore
  63. 2026-06-14 23:15 UTCEPSS rescore
  64. 2026-06-14 23:15 UTCEPSS rescore
  65. 2026-06-14 22:43 UTCOSV refresh
  66. 2026-06-13 22:58 UTCEPSS rescore
  67. 2026-06-12 23:09 UTCEPSS rescore
  68. 2026-06-11 13:58 UTCEPSS rescore
  69. 2026-06-11 13:58 UTCEPSS rescore
  70. 2026-06-10 22:16 UTCEPSS rescore
  71. 2026-06-10 13:19 UTCEPSS rescore
  72. 2026-06-08 14:15 UTCEPSS rescore
  73. 2026-06-08 14:14 UTCEPSS rescore
  74. 2026-06-07 15:23 UTCEPSS rescore
  75. 2026-06-07 15:22 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-12838?
CVE-2019-12838 is a critical vulnerability published on July 11, 2019. SchedMD Slurm 17.11.x, 18.08.0 through 18.08.7, and 19.05.0 allows SQL Injection.
When was CVE-2019-12838 disclosed?
CVE-2019-12838 was first published in the National Vulnerability Database on July 11, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-12838 actively exploited?
CVE-2019-12838 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3% probability of exploitation in the next 30 days, which ranks it in the top 15.4% of all scored CVEs.
What is the CVSS score of CVE-2019-12838?
CVE-2019-12838 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-12838?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-12838, 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-2019-12838

Explore →

Is Your Infrastructure Affected by CVE-2019-12838?

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

Start Free Scan →Browse All CVEs