# CVE-2026-12879: Cross-Tenant Data Exfiltration in Apigee via BigQuery Confused Deputy

> An authenticated attacker can exfiltrate cross-tenant data from Google Cloud Apigee via a confused deputy vulnerability in BigQuery integration.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:L/U:Clear`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-974p-4xqx-2m2q

## What is CVE-2026-12879?

CVE-2026-12879 is a medium-severity vulnerability in Google Cloud Apigee, published on 9 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An Improper Input Validation vulnerability in BigQuery DAO in Google Cloud Apigee versions prior to 2026-06-12 on Google Cloud Platform allows an authenticated attacker to exfiltrate cross-tenant data.

This vulnerability was patched on 12 June 2026 on the Apigee Servers, and no customer action is needed.

Weakness: CWE-610 (Externally Controlled Reference to a Resource in Another Sphere), CWE-441 (Unintended Proxy or Intermediary)

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


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

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

## Is CVE-2026-12879 being exploited?

There is no known exploitation of CVE-2026-12879 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12879 is a medium-severity vulnerability in Google Cloud Apigee, published on 9 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12879 in the wild and no public exploit code.

Affected product: Google Cloud Apigee. 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-12879/ (Markdown: https://insights.sbomify.com/CVE-2026-12879/index.md)
```

## Sources

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

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