No exploitation reportedFix available

CVE-2016-10030

No exploitation reported by the sources we read.

Published2017-01-05
WeaknessCWE-284

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The _prolog_error function in slurmd/req.c in Slurm before 15.08.13, 16.x before 16.05.7, and 17.x before 17.02.0-pre4 has a vulnerability in how the slurmd daemon informs users of a Prolog failure on a compute node. That vulnerability could allow a user to assume control of an arbitrary file on the system. Any exploitation of this is dependent on the user being able to cause or anticipate the failure (non-zero return code) of a Prolog script that their job would run on. This issue affects all Slurm versions from 0.6.0 (September 2005) to present. Workarounds to prevent exploitation of this are to either disable your Prolog script, or modify it such that it always returns 0 ("success") and adjust it to set the node as down using scontrol instead of relying on the slurmd to handle that automatically. If you do not have a Prolog set you are unaffected by this issue.

Timeline

dates in UTC

2017-01-0511:59CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-10030?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-10030?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Schedmd slurm

Branch	Affected	Fixed in	Source
15.8	≤ 15.08.12	no fix published	NVD
16.5	= 16.05.0	no fix published	NVD
16.5	= 16.05.1	no fix published	NVD
16.5	= 16.05.2	no fix published	NVD
16.5	= 16.05.3	no fix published	NVD
16.5	= 16.05.4	no fix published	NVD
16.5	= 16.05.5	no fix published	NVD
16.5	= 16.05.6	no fix published	NVD
17.2	= 17.02.0	no fix published	NVD

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

github.comPatch · Vendor Advisory
www.schedmd.comMitigation · Vendor Advisory

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVSS 3.08.1read 2026-10-23
NVDCVSS 2.07.6read 2026-10-23
NVDweakness (CWE)CWE-284read 2026-10-23
FIRST EPSSEPSS score2.5 %2026-10-22

Technical details

CVSS v3 Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Published: 2017-01-05
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2016-10030?

Is CVE-2016-10030 actively exploited?

Active exploitation of CVE-2016-10030 has not been confirmed. Its EPSS score was 2.5% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2016-10030?

CVE-2016-10030 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database