Skip to content
Vulnerability Intelligence

CVE-2024-28255

CriticalExploitedPublic exploit

The JwtFilter handles the API authentication by requiring and verifying JWT tokens.

Published Mar 15, 2024 · Updated Aug 12, 2026 · Also known as GHSA-6wx7-qw5p-wh84

Key Facts

Patch immediately
  • CVE-2024-28255 is a critical-severity vulnerability (CVSS 9.8 v3.1) affecting OpenMetadata (Open-Metadata).
  • It is exploited in the wild, listed in Industry KEV feed, CIRCL KEV since Apr 17, 2024. Public exploit code is available.
  • EPSS estimates a 73% probability of exploitation in the next 30 days.
  • Fixed versions are available, including OpenMetadata 1.2.4.
  • Brandefense priority: patch immediately, because it is listed as exploited in the wild.

CVSS v3.1

9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS (30-day exploit likelihood)

73%

Higher than 99.4% of all scored CVEs

Exploited in the wild

Yes

2 catalog listings

Public exploit code

Available

Proof-of-concept or weaponized module

Get the full CVE-2024-28255 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

Description

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.

Known-Exploited Catalog Listings

CatalogAddedRemediation dueRansomware use
Industry KEV feedApr 17, 2024n/aNot reported
CIRCL KEVApr 20, 2024n/aNot reported

Required action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Affected Products

2 affected entries in total
ProductAffected versionsFixed in
OpenMetadataOpen-Metadata>= < 1.2.41.2.4

Patched Releases

OpenMetadata

1.2.4

Timeline

  1. Publicly disclosed

    Mar 15, 2024

  2. Added to Industry KEV feed

    Apr 17, 2024

  3. Added to CIRCL KEV

    Apr 20, 2024

  4. Last updated

    Aug 12, 2026

Weakness Type

  • CWE-287 Improper Authentication

References

12 more references in the full CVE brief

FAQ

Common Questions.

Is CVE-2024-28255 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.

Request A Demo