CVE-2026-81029

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-26. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
8.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists open-metadata OpenMetadata versions before 2.0.0 as affected. No release containing a fix is confirmed on record.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
44th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 26, 2026

Last Modified

September 16, 2026

Advisory Details (4)

Auto-updated Aug 26, 2026
No fix on record yet. Sources: github.
Web page

OpenMetadata before 2.0.0 JWT Disclosure via Unvalidated SAML and OIDC Redirect URI | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openmetadata-before-2.0.0-jwt-disclosure-via-unvalidated-saml-and-oidc-redirect-uri
GitHub advisory

OpenMetadata/openmetadata-service/src/main/java/org/openmetadata/service/security/saml/SamlLoginServlet.java at 1.12.1 · open-metadata/OpenMetadata · GitHub

https://github.com/open-metadata/OpenMetadata/blob/1.12.1/openmetadata-service/src/main/java/org/openmetadata/service/security/saml/SamlLoginServlet.java
Web page

Open Redirect + JWT Token Leakage in SAML/OIDC Login Flows · Issue #29662 · open-metadata/OpenMetadata · GitHub

https://github.com/open-metadata/OpenMetadata/issues/29662
Web page

GitHub - open-metadata/OpenMetadata: The Open Context Layer for Data and AI , OpenMetadata is the open platform for building trusted data context and business semantics for humans, AI assistants, and agents. · GitHub

https://github.com/open-metadata/OpenMetadata

Vendor Advisories for CVE-2026-81029(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 102× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 174 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 74 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  2. 2026-10-13 06:23 UTCEG score recompute
  3. 2026-10-13 06:23 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  5. 2026-10-12 14:57 UTCEG score recompute
  6. 2026-10-11 19:21 UTCEG score recompute
  7. 2026-10-11 16:37 UTCEG score recompute
  8. 2026-10-11 13:55 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  11. 2026-10-10 06:06 UTCEG score recompute
  12. 2026-10-10 06:06 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  14. 2026-10-09 03:22 UTCEG score recompute
  15. 2026-10-09 03:22 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  16. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  17. 2026-10-08 01:50 UTCEG score recompute
  18. 2026-10-08 01:49 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  20. 2026-10-07 03:48 UTCEG score recompute
  21. 2026-10-07 03:48 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  22. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  23. 2026-10-06 15:04 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  24. 2026-10-06 01:41 UTCEG score recompute
  25. 2026-10-06 01:41 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
Show 75 more
  1. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  2. 2026-10-05 08:25 UTCEG score recompute
  3. 2026-10-05 08:25 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  5. 2026-10-04 19:41 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  6. 2026-10-04 04:51 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  7. 2026-10-03 16:06 UTCEG score recompute
  8. 2026-10-03 16:06 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  9. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  10. 2026-10-02 22:59 UTCEG score recompute
  11. 2026-10-02 22:59 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  13. 2026-10-02 10:07 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  14. 2026-10-01 21:24 UTCEG score recompute
  15. 2026-10-01 21:24 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  16. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  17. 2026-10-01 08:41 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  18. 2026-09-30 19:58 UTCEG score recompute
  19. 2026-09-30 19:58 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  20. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  21. 2026-09-30 06:03 UTCEG score recompute
  22. 2026-09-30 06:03 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-09-29 12:26 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  24. 2026-09-28 23:42 UTCEG score recompute
  25. 2026-09-28 23:42 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  26. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  27. 2026-09-28 10:58 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  28. 2026-09-27 22:15 UTCEG score recompute
  29. 2026-09-27 22:15 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  30. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  31. 2026-09-27 09:28 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  32. 2026-09-26 20:35 UTCEG score recompute
  33. 2026-09-26 20:35 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  34. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  35. 2026-09-25 16:36 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  36. 2026-09-25 03:21 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  37. 2026-09-24 14:37 UTCEG score recompute
  38. 2026-09-24 14:37 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  39. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  40. 2026-09-24 01:35 UTCEG score recompute
  41. 2026-09-24 01:34 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  42. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  43. 2026-09-23 12:51 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  44. 2026-09-23 00:08 UTCEG score recompute
  45. 2026-09-23 00:08 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  46. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  47. 2026-09-22 11:25 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  48. 2026-09-21 22:41 UTCEG score recompute
  49. 2026-09-21 22:41 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  50. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  51. 2026-09-21 09:58 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  52. 2026-09-20 21:14 UTCEG score recompute
  53. 2026-09-20 21:14 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  54. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  55. 2026-09-20 08:31 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  56. 2026-09-19 18:53 UTCEG score recompute
  57. 2026-09-19 18:53 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  58. 2026-09-19 06:06 UTCEG score recompute
  59. 2026-09-19 06:06 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  60. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  61. 2026-09-18 17:22 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  62. 2026-09-18 04:39 UTCEG score recompute
  63. 2026-09-18 04:39 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  64. 2026-09-17 15:56 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  65. 2026-09-17 03:13 UTCEG score recompute
  66. 2026-09-17 03:13 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  67. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  68. 2026-09-16 13:46 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  69. 2026-09-16 12:34 UTCEG score recompute
  70. 2026-09-16 12:34 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  71. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  72. 2026-09-15 23:51 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  73. 2026-09-15 11:08 UTCEG score recompute
  74. 2026-09-15 11:08 UTCGHSA enrichmentGHSA-j399-mfvr-j893 · GitHub severity HIGH · GitHub CVSS 8.1
  75. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 22nd percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81029?
CVE-2026-81029 is a high-severity vulnerability; its CVE record was published on August 26, 2026. 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…
When was CVE-2026-81029 made public?
CVE-2026-81029 was made public on August 26, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 26, 2026. EchelonGraph's copy of the record carries a last-modified date of September 16, 2026; the record at its source may have been updated since.
Is CVE-2026-81029 actively exploited?
CVE-2026-81029 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81029?
CVE-2026-81029 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-81029?
No fix for CVE-2026-81029 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists open-metadata OpenMetadata versions before 2.0.0 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-81029 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-81029

Explore →

Is Your Infrastructure Affected by CVE-2026-81029?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs