Categories
CVE-2026-46481 high CVSS 8.3

Vulnerability in org.open-metadata:openmetadata-service (CVE-2026-46481)

Summary

Vulnerability in org.open-metadata:openmetadata-service (CVE-2026-46481). Confidential information can be exposed externally. Exploitable via POST /api/v1/automations/workflows. Mitigation: upgrade to 1.12.4 or later.

Original description

The description as published by the source.

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 password in request.connection.config.password and the ingestion bot JWT in openMetadataServerConnection.securityConfig.jwtToken. The leaked ingestion-bot token can then be reused as Authorization: Bearer to access sensitive service APIs with bot-level privileges. This issue has been patched in version 1.12.4.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-46481 has been found in org.open-metadata:openmetadata-service.
Attackers can target a specific entry point like POST /api/v1/automations/workflows over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.3/10.
What to do: upgrade org.open-metadata:openmetadata-service to 1.12.4 or later.
If unsure, ask your IT team or search "org.open-metadata:openmetadata-service CVE-2026-46481" on the vendor's site.

CVE-2026-46481 (org.open-metadata:openmetadata-service) — CWE-201 / CVSS v3 8.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/v1/automations/workflows / GET /api/v1/services/databaseServices/{id} / GET /api/v1/system/version / GET /api/v1/services/databaseServices/f0382c0b-149e-4ca5-8844-d636c3437b9d
Patched: 1.12.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-201) exists in org.open-metadata:openmetadata-service. Attackers reach the vulnerable code path via POST /api/v1/automations/workflows.

📍 Affected scope

Check the vendor advisory for the affected versions of org.open-metadata:openmetadata-service. Attack surface: POST /api/v1/automations/workflows / GET /api/v1/services/databaseServices/{id} / GET /api/v1/system/version / GET /api/v1/services/databaseServices/f0382c0b-149e-4ca5-8844-d636c3437b9d.

🔥 Severity

Severity: High (CVSS 8.3/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.12.4.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /api/v1/automations/workflows requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.open-metadata:openmetadata-service を使っているサービスとバージョンを洗い出す。

  2. 2
    Hunt for indicators of compromise detect
    grep 'POST /api/v1/automations/workflows' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/v1/automations/workflows への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade org.open-metadata:openmetadata-service to 1.12.4

    ステージング環境で 1.12.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against POST /api/v1/automations/workflows on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

maven org.open-metadata:openmetadata-service
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.12.4"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details