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.
CVE-2026-80049
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.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
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 computedSeverity88% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 25, 2026
Advisory Details (4)
Auto-updated Aug 25, 2026Airbyte 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-workspaceidairbyte-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.ktoss/airbyte-platform.md at main · geo-chen/oss · GitHub
https://github.com/geo-chen/oss/blob/main/airbyte-platform.mdGitHub - airbytehq/airbyte-platform: The platform that powers Airbyte. Please file issues in https://github.com/airbytehq/airbyte · GitHub
https://github.com/airbytehq/airbyte-platformVendor 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 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-08-28 00:16 UTCEG score recompute
- 2026-08-28 00:16 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 11:17 UTCGHSA enrichment
- 2026-08-26 22:20 UTCEG score recompute
- 2026-08-26 22:20 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 09:22 UTCEG score recompute
- 2026-08-26 09:22 UTCGHSA enrichment
- 2026-08-25 19:20 UTCEG score recompute
- 2026-08-25 18:30 UTCEG score recompute
- 2026-08-25 18:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS p94CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS p94CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS p97CRITICAL
- CVE-2019-13360EG 9.8EPSS p98CRITICAL
- CVE-2019-12866EG 9.8CRITICAL
- CVE-2019-9756EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-80049?
When was CVE-2026-80049 disclosed?
Is CVE-2026-80049 actively exploited?
What is the CVSS score of CVE-2026-80049?
How do I remediate CVE-2026-80049?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-80049
Is Your Infrastructure Affected by CVE-2026-80049?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.