CVE-2024-28255

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 73.3%, top 1% 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
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 73%
  • Public exploit code is available (Metasploit, ssvc poc, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 73%CVSS: 9.8Exploit: Metasploit · ssvc poc · epss top5pct · epss high · public exploitExposed: 0

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

OpenMetadata is a unified platform for discovery, observability, and governance powered by a central metadata repository, in-depth lineage, and seamless team collaboration. The JwtFilter handles the API authentication by requiring and verifying JWT tokens. When a new request comes in, the request's path is checked against this list. When the request's path contains any of the excluded endpoints the filter returns without validating the JWT. Unfortunately, an attacker may use Path Parameters to make any path contain any arbitrary strings. For example, a request to GET /api/v1;v1%2fusers%2flogin/events/subscriptions/validation/condition/111 will match the excluded endpoint condition and therefore will be processed with no JWT validation allowing an attacker to bypass the authentication mechanism and reach any arbitrary endpoint, including the ones listed above that lead to arbitrary SpEL expression injection. This bypass will not work when the endpoint uses the SecurityContext.getUserPrincipal() since it will return null and will throw an NPE. This issue may lead to authentication bypass and has been addressed in version 1.2.4. Users are advised to upgrade. There are no known workarounds for this vulnerability. This issue is also tracked as GHSL-2023-237.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
88(Attend)
EG Risk 88/100SSVC: Attend

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%
Exploitation73% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
73%
EPSS %ILE
99%
KEV
Not listed

Published

March 15, 2024

Last Modified

September 4, 2025

Advisory Details (4)

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

Authentication bypass with path parameter in OpenMetadata (CVE-2024-28255) - vsociety

https://www.vicarius.io/vsociety/posts/authentication-bypass-with-path-parameter-in-openmetadata-cve-2024-28255
github Patch Available🟡 PoC Available

Authentication Bypass (`GHSL-2023-237`) · Advisory · open-metadata/OpenMetadata · GitHub

https://github.com/open-metadata/OpenMetadata/security/advisories/GHSA-6wx7-qw5p-wh84
github

OpenMetadata/openmetadata-service/src/main/java/org/openmetadata/service/security/JwtFilter.java at e2043a3f31312ebb42391d6c93a67584d798de52 · open-metadata/OpenMetadata · GitHub

https://github.com/open-metadata/OpenMetadata/blob/e2043a3f31312ebb42391d6c93a67584d798de52/openmetadata-service/src/main/java/org/openmetadata/service/security/JwtFilter.java#L113
github

OpenMetadata/openmetadata-service/src/main/java/org/openmetadata/service/security/JwtFilter.java at e2043a3f31312ebb42391d6c93a67584d798de52 · open-metadata/OpenMetadata · GitHub

https://github.com/open-metadata/OpenMetadata/blob/e2043a3f31312ebb42391d6c93a67584d798de52/openmetadata-service/src/main/java/org/openmetadata/service/security/JwtFilter.java#L111

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× 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.

  1. 2026-07-30 16:26 UTCEPSS rescore
  2. 2026-07-30 16:26 UTCEPSS rescore
  3. 2026-07-28 15:34 UTCEPSS rescore
  4. 2026-07-25 14:16 UTCEPSS rescore
  5. 2026-07-24 14:16 UTCEPSS rescore
  6. 2026-07-23 14:17 UTCEPSS rescore
  7. 2026-07-23 02:35 UTCEG score recompute
  8. 2026-07-22 14:07 UTCEPSS rescore
  9. 2026-07-21 15:23 UTCEPSS rescore
  10. 2026-07-20 17:06 UTCEPSS rescore
  11. 2026-07-19 02:28 UTCEPSS rescore
  12. 2026-07-19 02:28 UTCEPSS rescore
  13. 2026-07-18 10:03 UTCEPSS rescore
  14. 2026-07-18 10:03 UTCEPSS rescore
  15. 2026-07-16 17:01 UTCEPSS rescore
  16. 2026-07-15 16:56 UTCEPSS rescore
  17. 2026-07-15 16:56 UTCEPSS rescore
  18. 2026-07-14 16:55 UTCOSV refresh
  19. 2026-07-13 06:11 UTCEPSS rescore
  20. 2026-07-11 08:26 UTCEPSS rescore
  21. 2026-07-11 08:26 UTCEPSS rescore
  22. 2026-07-06 02:22 UTCEPSS rescore
  23. 2026-07-06 02:22 UTCEPSS rescore
  24. 2026-07-02 17:00 UTCEPSS rescore
  25. 2026-07-01 15:05 UTCEPSS rescore
Show 35 more
  1. 2026-06-30 23:21 UTCEPSS rescore
  2. 2026-06-30 23:21 UTCEPSS rescore
  3. 2026-06-28 14:06 UTCEPSS rescore
  4. 2026-06-28 14:06 UTCEPSS rescore
  5. 2026-06-28 04:55 UTCEPSS rescore
  6. 2026-06-28 04:55 UTCEPSS rescore
  7. 2026-06-26 17:39 UTCOSV refresh
  8. 2026-06-25 13:49 UTCEPSS rescore
  9. 2026-06-25 13:48 UTCEPSS rescore
  10. 2026-06-24 14:04 UTCEPSS rescore
  11. 2026-06-24 14:04 UTCEPSS rescore
  12. 2026-06-23 21:32 UTCEPSS rescore
  13. 2026-06-23 21:32 UTCEPSS rescore
  14. 2026-06-18 17:51 UTCEPSS rescore
  15. 2026-06-18 17:51 UTCEPSS rescore
  16. 2026-06-16 17:52 UTCEPSS rescore
  17. 2026-06-16 17:51 UTCEPSS rescore
  18. 2026-06-15 17:47 UTCEPSS rescore
  19. 2026-06-13 22:59 UTCEPSS rescore
  20. 2026-06-13 22:59 UTCEPSS rescore
  21. 2026-06-09 01:00 UTCOSV refresh
  22. 2026-06-06 13:46 UTCEPSS rescore
  23. 2026-06-06 13:46 UTCEPSS rescore
  24. 2026-06-05 22:46 UTCEPSS rescore
  25. 2026-06-05 22:46 UTCEPSS rescore
  26. 2026-06-01 13:51 UTCEPSS rescore
  27. 2026-06-01 13:51 UTCEPSS rescore
  28. 2026-06-01 13:51 UTCEPSS rescore
  29. 2026-05-29 13:43 UTCEPSS rescore
  30. 2026-05-29 13:43 UTCEPSS rescore
  31. 2026-05-27 13:40 UTCEPSS rescore
  32. 2026-05-27 13:40 UTCEPSS rescore
  33. 2026-05-26 07:18 UTCEPSS rescore
  34. 2026-05-26 07:18 UTCEPSS rescore
  35. 2026-05-24 06:40 UTCEG score recompute

Publicly available exploits

(3 references)

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

  • GitHub PoCYongYe-Security/CVE-2024-28255
    First seen Apr 12, 2024

    OpenMetadata_RCE (CVE-2024-28255) Batch scan/exploit

    Open source ↗
  • Metasploitexploit/linux/http/openmetadata_auth_bypass_rce✓ verified
    First seen Mar 15, 2024

    OpenMetadata authentication bypass and SpEL injection exploit chain

    Open source ↗
  • Nucleihttp/cves/2024/CVE-2024-28255.yaml
    First seen Jan 1, 2024

    OpenMetadata - Authentication Bypass

    Open source ↗

Frequently asked(5)

What is CVE-2024-28255?
CVE-2024-28255 is a critical vulnerability published on March 15, 2024. OpenMetadata is a unified platform for discovery, observability, and governance powered by a central metadata repository, in-depth lineage, and seamless team collaboration. The JwtFilter handles the API authentication by requiring and verifying JWT tokens. When a new request comes in, the request's…
When was CVE-2024-28255 disclosed?
CVE-2024-28255 was first published in the National Vulnerability Database on March 15, 2024, with the most recent update on September 4, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-28255 actively exploited?
CVE-2024-28255 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 73% probability of exploitation in the next 30 days, which ranks it in the top 0.6% of all scored CVEs.
What is the CVSS score of CVE-2024-28255?
CVE-2024-28255 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2024-28255?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-28255, 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-28255

Explore →

Is Your Infrastructure Affected by CVE-2024-28255?

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