CVE-2015-5224

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-13. 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: 4.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The mkostemp function in login-utils in util-linux when used incorrectly allows remote attackers to cause file name collision and possibly other attacks.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
61
EG Risk 61/100CISA SSVC

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%
Exploitation5% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
4.5%
EPSS %ILE
91st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 23, 2017

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Oct 7, 2026
Patch available. Sources: redhat, github_commit.
github_commit

commit bde91c85bdc7 (karelzak/util-linux)

Fix landed in karelzak/util-linux commit bde91c85bdc7 — awaiting tagged release

https://github.com/karelzak/util-linux/commit/bde91c85bdc77975155058276f99d2e0f5eab5a9
redhat

1256686 – (CVE-2015-5224) CVE-2015-5224 util-linux: File name collision due to incorrect mkstemp use

Affected: Red Hat Enterprise Linux 5 and 7. This issue does not affect the versions of util-linux-ng as shipped with Red Hat Enterprise

https://bugzilla.redhat.com/show_bug.cgi?id=1256686
generic

CVE-2015-5224 - PSIRT.COM

http://www.securityfocus.com/bid/76467
generic

oss-security - CVE-2015-5224 login-utils: file name collision due to incorrect mkstemp use

http://www.openwall.com/lists/oss-security/2015/08/24/3

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
util-linux—
  • every version up to 2.27-1: fixed in 2.27-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
util-linux—
  • every version up to 2.27-1: fixed in 2.27-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
util-linux—
  • every version up to 2.27-1: fixed in 2.27-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
util-linux—
  • every version up to 2.27-1: fixed in 2.27-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 25× 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 165 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2015-5224?
CVE-2015-5224 is a critical vulnerability published on August 23, 2017. The mkostemp function in login-utils in util-linux when used incorrectly allows remote attackers to cause file name collision and possibly other attacks.
When was CVE-2015-5224 disclosed?
CVE-2015-5224 was first published on August 23, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-5224 actively exploited?
CVE-2015-5224 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.5% probability of exploitation in the next 30 days (91st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2015-5224?
CVE-2015-5224 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2015-5224?
A fix for CVE-2015-5224 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-5224

Explore →

Is Your Infrastructure Affected by CVE-2015-5224?

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

Book a Demo →Browse All CVEs