Open-metadata vulnerabilities
We track 11 vulnerabilities in Open-metadata products. 11 are rated high or critical, and none are known to be exploited. The most recent was published on August 26, 2026.
Latest Open-metadata vulnerabilities
- 8.1 High severity
OpenMetadata: URL Redirection to Untrusted Site
OpenMetadata accepts a caller-supplied post-authentication redirect target and appends the issued token to it. SamlLoginServlet reads the callback request parameter and stores it in the HTTP session without comparing it against any configured or registered des
- 8.3 High severity
OpenMetadata: Insertion of Sensitive Information Into Sent Data
OpenMetadata is a unified metadata platform. Prior to version 1.12.4, a non-admin SSO user can trigger a TEST_CONNECTION workflow for a Database Service and receive, in the HTTP 201 response of POST /api/v1/automations/workflows, both the cleartext database pa
- 7.6 High severity
OpenMetadata: Improper Privilege Management
OpenMetadata is a unified metadata platform. Prior to 1.11.8, calls issued by the UI against /api/v1/ingestionPipelines leak JWTs used by ingestion-bot for certain services (Glue / Redshift / Postgres). Any read-only user can gain access to a highly privileged
- 7.2 High severity
OpenMetadata: Improper Control of Generation of Code
OpenMetadata is a unified metadata platform. Versions 1.5.0 through 1.11.3 are vulnerable to remote code execution via Server-Side Template Injection (SSTI) in FreeMarker email templates. An attacker must have administrative privileges to exploit the vulnerabi
- 8.8 High severity
Openmetadata: Improper Neutralization of Special Elements used in an SQL Command
OpenMetadata <=1.4.4 is vulnerable to SQL Injection. An attacker can extract information from the database in function listCount in the TestDefinitionDAO interface. The testPlatform parameter can be used to build a SQL query.
- 8.8 High severity
Openmetadata: Improper Neutralization of Special Elements used in an SQL Command
OpenMetadata <=1.4.1 is vulnerable to SQL Injection. An attacker can extract information from the database in function listCount in the WorkflowDAO interface. The workflowtype and status parameters can be used to build a SQL query.
- 8.8 High severity
OpenMetadata: Improper Control of Generation of Code
OpenMetadata is a unified platform for discovery, observability, and governance powered by a central metadata repository, in-depth lineage, and seamless team collaboration. The `CompiledRule::validateExpression` method evaluates an SpEL expression using an `S
- 8.8 High severity
OpenMetadata: Improper Control of Generation of Code
OpenMetadata is a unified platform for discovery, observability, and governance powered by a central metadata repository, in-depth lineage, and seamless team collaboration. Similarly to the GHSL-2023-250 issue, `AlertUtil::validateExpression` is also called fr
- 9.8 Critical severity
OpenMetadata: Improper Authentication
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. W
- 8.8 High severity
OpenMetadata: Improper Neutralization of Special Elements used in an OS Command
OpenMetadata is a unified platform for discovery, observability, and governance powered by a central metadata repository, in-depth lineage, and seamless team collaboration. The `AlertUtil::validateExpression` method evaluates an SpEL expression using `getValu
- 8.8 High severity
OpenMetadata: Improper Control of Generation of Code
OpenMetadata is a unified platform for discovery, observability, and governance powered by a central metadata repository, in-depth lineage, and seamless team collaboration. `CompiledRule::validateExpression` is also called from `PolicyRepository.prepare`. `pre