How severe is CVE-2019-6438?

CVE-2019-6438 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2019-6438 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (81st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-6438?

CVE-2019-6438 primarily affects Schedmd Slurm. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2019-6438?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2019-6438 published?

CVE-2019-6438 was published on 2019-01-31 and last updated on 2026-06-17.

CVE-2019-6438

CVE-2019-6438 is a critical-severity vulnerability in Schedmd Slurm with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 2% (81st percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Schedmd Slurm
Published: 2019-01-31
Last modified: 2026-06-17

Description

SchedMD Slurm before 17.11.13 and 18.x before 18.08.5 mishandles 32-bit systems.

Frequently asked questions

What is CVE-2019-6438?: SchedMD Slurm before 17.11.13 and 18.x before 18.08.5 mishandles 32-bit systems.
How severe is CVE-2019-6438?: CVE-2019-6438 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2019-6438 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (81st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-6438?: CVE-2019-6438 primarily affects Schedmd Slurm. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2019-6438?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2019-6438 published?: CVE-2019-6438 was published on 2019-01-31 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:a:schedmd:slurm:*:*:*:*:*:*:x86:*
cpe:2.3:o:opensuse:leap:15.0:*:*:*:*:*:*:*

More vulnerabilities in Schedmd Slurm

CVE-2023-49937 — Critical (CVSS 9.8): An issue was discovered in SchedMD Slurm 22.05.x, 23.02.x, and 23.11.x. Because of a double free, attackers can cause a…
CVE-2023-49934 — Critical (CVSS 9.8): An issue was discovered in SchedMD Slurm 23.11.x. There is SQL Injection against the SlurmDBD database. The fixed…
CVE-2022-29502 — Critical (CVSS 9.8): SchedMD Slurm 21.08.x through 20.11.x has Incorrect Access Control that leads to Escalation of Privileges.
CVE-2020-27745 — Critical (CVSS 9.8): Slurm before 19.05.8 and 20.x before 20.02.6 has an RPC Buffer Overflow in the PMIx MPI plugin.
CVE-2019-12838 — Critical (CVSS 9.8): SchedMD Slurm 17.11.x, 18.08.0 through 18.08.7, and 19.05.0 allows SQL Injection.
CVE-2018-7033 — Critical (CVSS 9.8): SchedMD Slurm before 17.02.10 and 17.11.x before 17.11.5 allows SQL Injection attacks against SlurmDBD.

All CVEs affecting Schedmd Slurm →