CVE-2024-28189

CRITICALNVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 7.2% (94th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
10.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Metasploit, ssvc poc, public exploit)
CISA-KEV: Not listedEPSS PROB: 7.2%CVSS: 10.0Exploit: Metasploit · ssvc poc · public exploitExposed services: Not assessed

The CVE record names the fixed release — apply it.

Judge0 is an open-source online code execution system. The application uses the UNIX chown command on an untrusted file within the sandbox. An attacker can abuse this by creating a symbolic link (symlink) to a file outside the sandbox, allowing the attacker to run chown on arbitrary files outside of the sandbox. This vulnerability is not impactful on it's own, but it can be used to bypass the patch for CVE-2024-28185 and obtain a complete sandbox escape. This vulnerability is fixed in 1.13.1.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
86
EG Risk 86/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
Severity100% × 45%
Exploitation65% × 40%
Automatability100% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
7.2%
EPSS %ILE
94th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (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

April 18, 2024

Last Modified

April 15, 2026

Advisory Details (4)

Auto-updated Oct 3, 2026
🔬 Proof of concept available. Fix named in the CVE record. Sources: github_commit, github.
githubMentions a patch (unverified)🟡 PoC Available

Sandbox Escape via Symbolic Link · Advisory · judge0/judge0 · GitHub

https://github.com/judge0/judge0/security/advisories/GHSA-h9g2-45c8-89cf
githubMentions a patch (unverified)🟡 PoC Available

Sandbox Escape Patch Bypass via chown running on Symbolic Link · Advisory · judge0/judge0 · GitHub

https://github.com/judge0/judge0/security/advisories/GHSA-3xpw-36v7-2cmg
github_commit

commit f3b8547b3b67 (judge0/judge0)

Fix landed in judge0/judge0 commit f3b8547b3b67 — awaiting tagged release

https://github.com/judge0/judge0/commit/f3b8547b3b67863e4ea0ded3adcb963add56addd
generic

judge0/app/jobs/isolate_job.rb at v1.13.0 · judge0/judge0 · GitHub

https://github.com/judge0/judge0/blob/v1.13.0/app/jobs/isolate_job.rb#L232

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitexploit/linux/http/judge0_sandbox_escape_cve_2024_28189✓ verified
    First seen Mar 4, 2024

    Judge0 sandbox escape

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-28189?
CVE-2024-28189 is a critical vulnerability published on April 18, 2024. Judge0 is an open-source online code execution system. The application uses the UNIX chown command on an untrusted file within the sandbox. An attacker can abuse this by creating a symbolic link (symlink) to a file outside the sandbox, allowing the attacker to run chown on arbitrary files outside…
When was CVE-2024-28189 disclosed?
CVE-2024-28189 was first published on April 18, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-28189 actively exploited?
CVE-2024-28189 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 7.2% probability of exploitation in the next 30 days (94th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-28189?
CVE-2024-28189 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2024-28189?
The CVE record for CVE-2024-28189 names the fix: "This vulnerability is fixed in 1.13.1."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-28189

Explore →

Is Your Infrastructure Affected by CVE-2024-28189?

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

Book a Demo →Browse All CVEs