# CVE-2025-13292: Improper access control in Google Cloud Apigee-X allows cross-tenant Analytics modification and log data access.

> Attackers can access and modify analytics data and logs from other customer organizations due to improper access controls in Apigee-X.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N/U:Clear`)
- **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:** 6 Dec 2025
- **Updated:** 30 Jan 2026
- **Also known as:** GHSA-rwr4-4f3w-p582

## What is CVE-2025-13292?

CVE-2025-13292 is a high-severity missing authorization vulnerability in Google Cloud Apigee-X, published on 6 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in Apigee-X allowed an attacker to gain unauthorized read and write access to Apigee Analytics (AX) data and access logs belonging to other Apigee customer organizations.

Apigee-X was found to be vulnerable.

This vulnerability was patched in version 1-16-0-apigee-3. No user action is required for this.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-13292?


## How do I fix CVE-2025-13292?

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

## Is CVE-2025-13292 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13292 and fix it if it is affected.

What it is: CVE-2025-13292 is a high-severity missing authorization vulnerability in Google Cloud Apigee-X, published on 6 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13292 in the wild and no public exploit code.

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

## Sources

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

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