CVE-2026-80049

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. A secondary CVSS source baseline 8.8; 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 week
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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

Airbyte Platform resolves the workspace used for its authorization decision from a field the caller supplies. AuthorizationServerHandler copies recognised identifiers out of the raw JSON request body into X-Airbyte-* headers, and AuthenticationHeaderResolver.resolveWorkspace consults X-Airbyte-Workspace-Id ahead of every resource-derived header, including those for connection, source and destination identifiers. Endpoints whose declared request bodies carry only a resource identifier are nonetheless reached with an added workspaceId field, because the extractor reads the body rather than the endpoint's schema, so the permission check is performed against the workspace the caller nominated while the handler acts on the resource identifier the caller supplied. Nothing afterwards compares the resource's owning workspace with the one that was authorized. A member of any workspace can therefore read source and destination configuration, trigger and cancel syncs, and delete connections, sources and destinations that belong to workspaces they have no access to, at whatever privilege level their own workspace membership grants them.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CVSS v4.0 confidentiality and integrity impact both High). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 25, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Aug 25, 2026
No fix on record yet.
Web page

Airbyte Platform through 2.0.0 Cross-Workspace Authorization Bypass via Caller-Supplied workspaceId | Advisories | VulnCheck

https://www.vulncheck.com/advisories/airbyte-platform-through-2.0.0-cross-workspace-authorization-bypass-via-caller-supplied-workspaceid
Web page

airbyte-platform/airbyte-commons-server/src/main/kotlin/io/airbyte/commons/server/support/AuthenticationHeaderResolver.kt at v2.0.0 · airbytehq/airbyte-platform · GitHub

https://github.com/airbytehq/airbyte-platform/blob/v2.0.0/airbyte-commons-server/src/main/kotlin/io/airbyte/commons/server/support/AuthenticationHeaderResolver.kt
Web page

oss/airbyte-platform.md at main · geo-chen/oss · GitHub

https://github.com/geo-chen/oss/blob/main/airbyte-platform.md
Web page

GitHub - airbytehq/airbyte-platform: The platform that powers Airbyte. Please file issues in https://github.com/airbytehq/airbyte · GitHub

https://github.com/airbytehq/airbyte-platform

Vendor Advisories for CVE-2026-80049(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 21× in last 7d / 101× 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 99 of 168 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 69 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-80049?
CVE-2026-80049 is a high-severity vulnerability; its CVE record was published on August 25, 2026. Airbyte Platform resolves the workspace used for its authorization decision from a field the caller supplies. AuthorizationServerHandler copies recognised identifiers out of the raw JSON request body into X-Airbyte-* headers, and AuthenticationHeaderResolver.resolveWorkspace consults…
When was CVE-2026-80049 made public?
CVE-2026-80049 was made public on August 25, 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 25, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-80049 actively exploited?
CVE-2026-80049 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80049?
CVE-2026-80049 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-80049?
No fix for CVE-2026-80049 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 vendor advisories EchelonGraph has for CVE-2026-80049 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-80049?

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

Book a Demo →Browse All CVEs