{"answers":{"affected":"2 open source packages ship an affected version, including org.open-metadata:openmetadata-sdk. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-26010 exists.","fix":"Upgrade org.open-metadata:openmetadata-sdk to 1.11.8 or later.","what":"CVE-2026-26010 is a high-severity vulnerability in open-metadata OpenMetadata, published on 11 Feb 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-26010 and fix it if it is affected.\n\nWhat it is: CVE-2026-26010 is a high-severity vulnerability in open-metadata OpenMetadata, published on 11 Feb 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-26010 exists.\n\nAffected packages and fixed versions:\n- org.open-metadata:openmetadata-sdk (Maven): affected all versions; fixed in 1.11.8\n- org.open-metadata:openmetadata-sdk (Maven): affected all versions; fixed in 1.11.8\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-26010/ (Markdown: https://insights.sbomify.com/CVE-2026-26010/index.md)","id":"CVE-2026-26010","markdown":"https://insights.sbomify.com/CVE-2026-26010/index.md","name":"CVE-2026-26010","record":{"aliases":["GHSA-pqqf-7hxm-rj5r"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenMetadata platform","requires_auth":"low_privilege","summary":"Read-only users can steal privileged JWTs from API responses to gain Ingestion Bot role, enabling destructive changes and data leakage.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"openmetadata","vendor":"open-metadata"}],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L","version":"3.0"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"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 account, typically which has the Ingestion Bot Role. This enables destructive changes in OpenMetadata instances, and potential data leakage (e.g. sample data, or service metadata which would be unavailable per roles/policies). This vulnerability is fixed in 1.11.8.","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":"Leaky JWTs in OpenMetadata exposing highly-privileged bot users","id":"CVE-2026-26010","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Memory corruption in navigation2","id":"CVE-2026-26011"},"packages":[{"ecosystem":"Maven","fixed":["1.11.8"],"introduced":["0"],"last_affected":[],"package":"org.open-metadata:openmetadata-sdk","purl":null,"source":"GHSA-pqqf-7hxm-rj5r"},{"ecosystem":"Maven","fixed":["1.11.8"],"introduced":["0"],"last_affected":[],"package":"org.open-metadata:openmetadata-sdk","purl":"pkg:maven/org.open-metadata/openmetadata-sdk","source":"GHSA-pqqf-7hxm-rj5r"}],"prev":{"headline":"Catalyst Affected by Remote Code Execution as Root via Containerized Install Script Execution","id":"CVE-2026-26009"},"products":["OpenMetadata"],"published":"2026-02-11","related":[{"cvss_score":9.8,"headline":"Authentication Bypass in OpenMetadata","id":"CVE-2024-28255","kev_date_added":null,"published":"2024-03-15"},{"cvss_score":9.4,"headline":"SpEL Injection in `PUT /api/v1/policies` in OpenMetadata","id":"CVE-2024-28253","kev_date_added":null,"published":"2024-03-15"},{"cvss_score":8.8,"headline":"SpEL Injection in `GET /api/v1/events/subscriptions/validation/condition/\u003cexpr\u003e` in OpenMetadata","id":"CVE-2024-28254","kev_date_added":null,"published":"2024-03-15"},{"cvss_score":8.8,"headline":"SpEL Injection in `PUT /api/v1/events/subscriptions` in OpenMetadata","id":"CVE-2024-28847","kev_date_added":null,"published":"2024-03-15"},{"cvss_score":8.8,"headline":"SpEL Injection in `GET /api/v1/policies/validation/condition/\u003cexpr\u003e` in OpenMetadata","id":"CVE-2024-28848","kev_date_added":null,"published":"2024-03-15"},{"cvss_score":8.5,"headline":"OpenMetadata Server-Side Template Injection (SSTI) in FreeMarker email templates that leads to RCE","id":"CVE-2026-22244","kev_date_added":null,"published":"2026-01-08"}],"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":"US public information, NVD API terms","name":"NVD"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-02-12","vendors":["open-metadata"]},"summary":"Read-only users can steal privileged JWTs from API responses to gain Ingestion Bot role, enabling destructive changes and data leakage.","url":"https://insights.sbomify.com/CVE-2026-26010/"}