OpenMetadata's Server-Side Template Injection (SSTI) in FreeMarker email templates leads to RCE

Exploitation

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

CVSS 4.0

8.5 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P · score source

EPSS

• CVE-2026-22244: 1.29% estimated exploitation activity in the next 30 days; percentile 70.17 (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.

OpenMetadata RCE Vulnerability - Proof of Concept Executive Summary CRITICAL Remote Code Execution vulnerability confirmed in OpenMetadata v1.11.2 via Server-Side Template Injection (SSTI) in FreeMarker email templates. Credit - @lnlinh31, @satthusaosan, @TheMacCuoi, @get-wright, @Ohnooo1234, @hienduc14 – FPT Cloud AppSec Research Team, FPT Smart Cloud Vulnerability Details 1. Root Cause File: openmetadata-service/src/main/java/org/openmetadata/service/util/DefaultTemplateProvider.java Lines 35-45 contain unsafe FreeMarker template instantiation: Missing Security Controls: - ❌ No setNewBuiltinClassResolver(TemplateClassResolver.SAFERRESOLVER) - Allows arbitrary class instantiation - ❌ No setAPIBuiltinEnabled(false) - Enables ?api built-in for reflection - ❌ No input validation - Template content not sanitized 2. Attack Vector (VERIFIED) Step 1: Attacker with Admin role modifies EmailTemplate via PATCH endpoint Step 2: Malicious template stored in MySQL database: Step 3: Trigger…

Published by the source

7 Jan 2026, 19:33 UTC

Last modified by the source

31 Aug 2026, 23:00 UTC

Source last checked

26 Oct 2026, 16:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5f29-2333-h9c7

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

# Patch Next advisory brief: CVE-2026-22244

Advisory: OpenMetadata's Server-Side Template Injection (SSTI) in FreeMarker email templates leads to RCE
IDs: CVE-2026-22244, GHSA-5f29-2333-h9c7
Record: https://patchnext.com/advisories/cve-2026-22244 (revision 1, source checked 26 Oct 2026, 16:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
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:platform 1.11.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.open-metadata:platform: affected >= 1.5.0, < 1.11.4; fixed in 1.11.4

## Suggested inspection (read-only)
- Maven org.open-metadata:platform: 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:platform.
- 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-5f29-2333-h9c7 (GitHub-reviewed advisory GHSA-5f29-2333-h9c7 lists affected ranges: Maven org.open-metadata:platform >=1.5.0 <1.11.4)

Commands are suggestions: review each one before running it.