{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81029 exists.","fix":"No fix has been published for CVE-2026-81029 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81029 is a high-severity vulnerability in open-metadata OpenMetadata, published on 26 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-81029 and fix it if it is affected.\n\nWhat it is: CVE-2026-81029 is a high-severity vulnerability in open-metadata OpenMetadata, published on 26 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81029 exists.\n\nAffected product: open-metadata OpenMetadata. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-81029/ (Markdown: https://insights.sbomify.com/CVE-2026-81029/index.md)","id":"CVE-2026-81029","markdown":"https://insights.sbomify.com/CVE-2026-81029/index.md","name":"CVE-2026-81029","record":{"aliases":["GHSA-3f34-r7gw-5f28","GHSA-j399-mfvr-j893"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenMetadata data catalog","requires_auth":"none","summary":"Attackers can steal JWT tokens via unvalidated redirect URIs in SAML/OIDC flows, leading to account takeover and data access.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"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 destination, and the assertion consumer servlet later formats that stored value into a URL carrying the freshly issued JWT together with the account's email and name before sending the redirect. The OIDC and OAuth2 handler follows the same pattern with its own redirect parameter and the issued identity token. A request naming a destination the attacker controls therefore causes the server to deliver a valid token for whoever completes the login to that destination. Because the token authenticates API calls as that account, a user who follows such a link and authenticates hands over control of their account. Version 2.0.0 removes the caller-supplied callback parameter; no 1.x release validates it.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"OpenMetadata before 2.0.0 JWT Disclosure via Unvalidated SAML and OIDC Redirect URI","id":"CVE-2026-81029","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Mage AI through 0.9.79 Arbitrary File Read via Unvalidated Path in browser_items Endpoint","id":"CVE-2026-81030"},"packages":[],"prev":{"headline":"ZLMediaKit downloadFile Root-Directory Confinement Bypass via Prefix Collision","id":"CVE-2026-81028"},"products":["OpenMetadata"],"published":"2026-08-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-10-20","vendors":["open-metadata"]},"summary":"Attackers can steal JWT tokens via unvalidated redirect URIs in SAML/OIDC flows, leading to account takeover and data access.","url":"https://insights.sbomify.com/CVE-2026-81029/"}