GCVE-1988-2026-0388
Vulnerability from gna-1988 – Published: 2026-10-02 04:57 – Updated: 2026-10-02 04:57| URL | Tags |
|---|---|
| https://vuln.freearchive.org/archive/item/c9c5abc… | technical-description |
| https://lists.securityfocus.com/hyperkitty/list/b… | technical-description |
| https://security-tracker.debian.org/tracker/slurm-wlm | |
| https://www.debian.org/security/ | |
| https://www.debian.org/security/faq |
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| unknown | slurm-wlm security update |
Affected:
unknown
|
guessed |
{
"containers": {
"cna": {
"affected": [
{
"product": "slurm-wlm security update",
"vendor": "unknown",
"versions": [
{
"status": "affected",
"version": "unknown"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Aron Xu"
}
],
"descriptions": [
{
"lang": "en",
"value": "-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n- -------------------------------------------------------------------------\nDebian Security Advisory DSA-6491-1 security@debian.org\nhttps://www.debian.org/security/ Aron Xu\nSeptember 09, 2026 https://www.debian.org/security/faq\n- -------------------------------------------------------------------------\nPackage : slurm-wlm\nCVE ID : CVE-2026-65107 CVE-2026-65108 CVE-2026-65109 CVE-2026-65138\nCVE-2026-65139 CVE-2026-65140 CVE-2026-65165\nDebian Bug : 1146563\nSeveral vulnerabilities were discovered in the Slurm Workload Manager, a\ncluster resource management and job scheduling system, which may result\nin privilege escalation, SQL injection in the accounting database,\ndeletion of files outside the container spool directory, bypass of\ncredential verification for shared objects transferred with sbcast, or\ndenial of service.\nFor the stable distribution (trixie), these problems have been fixed in\nversion 24.11.5-4+deb13u1.\nWe recommend that you upgrade your slurm-wlm packages.\nFor the detailed security status of slurm-wlm please refer to\nits security tracker page at:\nhttps://security-tracker.debian.org/tracker/slurm-wlm\nFurther information about Debian Security Advisories, how to apply\nthese updates to your system and frequently asked questions can be\nfound at: https://www.debian.org/security/\nMailing list: debian-security-announce@lists.debian.org\n-----BEGIN PGP SIGNATURE-----\niQEzBAEBCAAdFiEExq6D0hxncEPaPayX+GQ1dHE8m64FAmqgz9EACgkQ+GQ1dHE8\nm67dxwf+IPgq5EL+BekNMrDNvX79m1rhvmSu5FOwVTUmhZJ7iCqgtxtaGQo1Wn7V\nw991Bj442i6Az4g4wYXyYRkoJxG9ez7N9d+m+039R/SdLy5gHz4B/pEtPohAIJ+i\nAPBSMXkQihpdp2dzBq1vJLe3aBBDGiF6XMcMxiimXjPr+90WsBSp+egQv/xbTIBC\nLexqhYs4v1N0bVuj+PzPN4YcFc9Zpm08aZ0Da5Fb0lwaARqGNUHVE/MbqFpxQNvB\nZHIURaPbWCoJwUOgVDbHAe3cdoDtl7hBe4+8fDLoHqiVn4qXx8oxucGZYTM4EqCI\naxKOO4oPO4+fZL7P5ET3FrZgyirXSA==\n=BpL9\n-----END PGP SIGNATURE-----"
}
],
"providerMetadata": {
"dateUpdated": "2026-10-02T04:57:26Z",
"orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"shortName": "VULNARCHIVE"
},
"references": [
{
"tags": [
"technical-description"
],
"url": "https://vuln.freearchive.org/archive/item/c9c5abcb7d8766158abdce4919f3f30e79141a0b1b9258749eedd234eca1b280"
},
{
"tags": [
"technical-description"
],
"url": "https://lists.securityfocus.com/hyperkitty/list/bugtraq@securityfocus.com/message/5JK2P5S7YQ4SJCJU3RVZRF4IEFKCBGON/"
},
{
"url": "https://security-tracker.debian.org/tracker/slurm-wlm"
},
{
"url": "https://www.debian.org/security/"
},
{
"url": "https://www.debian.org/security/faq"
}
],
"source": {
"defect": [
"E1x48pG-00000007Nji-3LjM%40seger.debian.org"
],
"discovery": "EXTERNAL"
},
"title": "[Bugtraq] [SECURITY] [DSA 6491-1] slurm-wlm security update",
"x_gcve": [
{
"recordType": "advisory",
"relationships": [],
"vulnId": "GCVE-1988-2026-0388",
"x_vulnarchive": {
"archiveUrl": "https://vuln.freearchive.org/archive/item/c9c5abcb7d8766158abdce4919f3f30e79141a0b1b9258749eedd234eca1b280",
"automated": true,
"contentSha256": "c9c5abcb7d8766158abdce4919f3f30e79141a0b1b9258749eedd234eca1b280",
"evidenceScore": 7,
"messageId": "E1x48pG-00000007Nji-3LjM%40seger.debian.org",
"originalUrl": "https://lists.securityfocus.com/hyperkitty/list/bugtraq@securityfocus.com/message/5JK2P5S7YQ4SJCJU3RVZRF4IEFKCBGON/",
"policy": "vulnarchive-1",
"sourceFormat": "text/html",
"sourcePublishedAt": "2026-10-02T04:57:26Z"
}
}
]
}
},
"cveMetadata": {
"assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
"assignerShortName": "VULNARCHIVE",
"datePublished": "2026-10-02T04:57:26Z",
"dateUpdated": "2026-10-02T04:57:26Z",
"state": "PUBLISHED",
"vulnId": "GCVE-1988-2026-0388"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.