CVE-2024-28189

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 57.6%, top 2% of all CVEs by exploit prediction. 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.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 7%CVSS: 10.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.0(medium)
EPSS
93.6%
KEV
Not listed

Published

April 18, 2024

Last Modified

April 15, 2026

Advisory Details (4)

Auto-updated Jul 10, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

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

https://github.com/judge0/judge0/security/advisories/GHSA-h9g2-45c8-89cf
github Patch Available🟡 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 12× in last 7d / 46× 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 103 total refreshes for this CVE.

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

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 in the National Vulnerability Database 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. FIRST EPSS estimates a 93.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-28189, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.