# CVE-2026-80049: Airbyte Platform through 2.0.0 Cross-Workspace Authorization Bypass via Caller-Supplied workspaceId

> Attackers can bypass workspace authorization to read, modify, or delete data integration resources in unauthorized workspaces by supplying a specific workspace ID.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-p5mw-j28v-ph9h

## What is CVE-2026-80049?

CVE-2026-80049 is a high-severity missing authorization vulnerability in airbytehq airbyte-platform, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-80049?


## How do I fix CVE-2026-80049?

No fix has been published for CVE-2026-80049 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-80049 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-80049 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80049 and fix it if it is affected.

What it is: CVE-2026-80049 is a high-severity missing authorization vulnerability in airbytehq airbyte-platform, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-80049 exists.

Affected product: airbytehq airbyte-platform. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80049/ (Markdown: https://insights.sbomify.com/CVE-2026-80049/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80049
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80049
- OSV: https://osv.dev/vulnerability/CVE-2026-80049

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80049/
Summaries are generated and may contain mistakes; the official description above is the record.