{"answers":{"affected":"2 open source packages ship an affected version, including org.open-metadata:openmetadata-service.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46481 exists.","fix":"Upgrade org.open-metadata:openmetadata-service to 1.12.4 or later.","what":"CVE-2026-46481 is a high-severity vulnerability in open-metadata OpenMetadata, published on 8 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46481 and fix it if it is affected.\n\nWhat it is: CVE-2026-46481 is a high-severity vulnerability in open-metadata OpenMetadata, published on 8 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46481 exists.\n\nAffected packages and fixed versions:\n- org.open-metadata:openmetadata-service (Maven): affected all versions; fixed in 1.12.4\n- org.open-metadata:openmetadata-service (Maven): affected all versions; fixed in 1.12.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-46481/ (Markdown: https://insights.sbomify.com/CVE-2026-46481/index.md)","id":"CVE-2026-46481","markdown":"https://insights.sbomify.com/CVE-2026-46481/index.md","name":"CVE-2026-46481","record":{"aliases":["GHSA-9vmh-whc4-7phg"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenMetadata platform","requires_auth":"low_privilege","summary":"Non-admin users can leak cleartext database passwords and ingestion-bot JWTs via the TEST_CONNECTION workflow, enabling unauthorized access to sensitive APIs.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-201","name":"Insertion of Sensitive Information Into Sent Data"}],"description":"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 \u003cjwt\u003e to access sensitive service APIs with bot-level privileges. This issue has been patched in version 1.12.4.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"OpenMetadata: TEST_CONNECTION workflow leaks ingestion-bot JWT and database password to regular users","id":"CVE-2026-46481","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"MyBB: Security Question insufficient validation","id":"CVE-2026-46482"},"packages":[{"ecosystem":"Maven","fixed":["1.12.4"],"introduced":["0"],"last_affected":[],"package":"org.open-metadata:openmetadata-service","purl":null,"source":"GHSA-9vmh-whc4-7phg"},{"ecosystem":"Maven","fixed":["1.12.4"],"introduced":["0"],"last_affected":[],"package":"org.open-metadata:openmetadata-service","purl":"pkg:maven/org.open-metadata/openmetadata-service","source":"GHSA-9vmh-whc4-7phg"}],"prev":{"headline":"Flowise: Evaluator create+update mass-assignment allows cross-workspace evaluator takeover","id":"CVE-2026-46480"},"products":["OpenMetadata"],"published":"2026-06-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-08","vendors":["open-metadata"]},"summary":"Non-admin users can leak cleartext database passwords and ingestion-bot JWTs via the TEST_CONNECTION workflow, enabling unauthorized access to sensitive APIs.","url":"https://insights.sbomify.com/CVE-2026-46481/"}