OpenMetadata vulnerable to a SpEL Injection in GET /api/v1/policies/validation/condition/ (GHSL-2023-236)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2024-28848: 7.89% estimated exploitation activity in the next 30 days; percentile 94.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

SpEL Injection in GET /api/v1/policies/validation/condition/<expr (GHSL-2023-236) Please note, only authenticated users have access to PUT / POST APIS for /api/v1/policies. Non authenticated users will not be able to access these APIs to exploit the vulnerability. A user must exist in OpenMetadata and have authenticated themselves to exploit this vulnerability. The ‎CompiledRule::validateExpression method evaluates an SpEL expression using an StandardEvaluationContext, allowing the expression to reach and interact with Java classes such as java.lang.Runtime, leading to Remote Code Execution. The /api/v1/policies/validation/condition/<expression endpoint passes user-controlled data CompiledRule::validateExpession allowing authenticated (non-admin) users to execute arbitrary system commands on the underlaying operating system. Snippet from PolicyResource.java In addition, there is a missing authorization check since Authorizer.authorize() is never called in the affected path and…

Published by the source

24 Apr 2024, 17:06 UTC

Last modified by the source

24 Apr 2024, 17:06 UTC

Source last checked

26 Oct 2026, 16:30 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5xv3-fm7g-865r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-28848

Advisory: OpenMetadata vulnerable to a SpEL Injection in `GET /api/v1/policies/validation/condition/ ` (`GHSL-2023-236`)
IDs: CVE-2024-28848, GHSA-5xv3-fm7g-865r
Record: https://patchnext.com/advisories/cve-2024-28848 (revision 1, source checked 26 Oct 2026, 16:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.open-metadata:openmetadata-service 1.2.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.open-metadata:openmetadata-service: affected < 1.2.4; fixed in 1.2.4

## Suggested inspection (read-only)
- Maven org.open-metadata:openmetadata-service: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.open-metadata:openmetadata-service.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5xv3-fm7g-865r (GitHub-reviewed advisory GHSA-5xv3-fm7g-865r lists affected ranges: Maven org.open-metadata:openmetadata-service >=0 <1.2.4)

Commands are suggestions: review each one before running it.