dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-13292

HIGH · 7.6 CVSS v4.0 Published 2025-12-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a multi-tenant authorization bypass vulnerability in Apigee-X where insufficient isolation between customer organizations allowed an attacker to read and write Apigee Analytics (AX) data and access logs belonging to other tenants. The flaw represents a cross-tenant data leakage/tampering issue in the shared Apigee-X infrastructure.

MitigationNo user action required as Google has automatically patched the vulnerability in version 1-16-0-apigee-3. Organizations should verify their Apigee-X instance is running the patched version and review analytics access logs for any anomalous cross-tenant activity around the disclosure period.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Clear

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Apigee-X version
    Use the Google Cloud Console or gcloud CLI to retrieve the Apigee-X instance version. In Cloud Console, navigate to the Apigee-X organization overview page where the version is displayed. Alternatively, run: gcloud apigee organizations describe ORG_NAME --format='get(annotations.version)'
    Affected if The displayed version is earlier than 1-16-0-apigee-3 (e.g., 1-14-x, 1-15-x) or the version field cannot be retrieved, indicating an unpatched environment
  2. Review analytics access logs for cross-tenant activity
    In Cloud Console, go to Apigee Analytics > Logs or use Cloud Logging with filter: resource.type="apigee.googleapis.com/Environment" AND logName="projects/PROJECT_ID/logs/apigee.googleapis.com%2Fanalytics_access". Look for access events where the organization ID differs from your own organization
    Affected if Any log entries show analytics data or logs being accessed by an organization ID that does not match your own organization identifier, indicating unauthorized cross-tenant access occurred
  3. Audit proxy traffic for unexpected data exposure
    Examine Apigee-X proxy traffic logs in Cloud Logging using: resource.type="apigee.googleapis.com/Proxy" AND logName contains "analytics". Check for any API calls to analytics endpoints that originate from unfamiliar organization identifiers or service accounts
    Affected if Proxy traffic logs reveal API calls to analytics endpoints where the caller organization does not match your organization, suggesting data was accessed or modified by another tenant
  4. Verify analytics data integrity
    Query your Apigee Analytics data sets (through the Analytics dashboard or API) and compare recent data volumes and timestamps against your expected traffic patterns. Look for data anomalies such as unexpected records, duplicate entries, or data gaps that could indicate tampering
    Affected if Analytics data shows unexpected records, unauthorized organization identifiers in metadata, or data inconsistencies that cannot be attributed to your own traffic

Your environment is affected if you were running any Apigee-X version prior to 1-16-0-apigee-3 OR if your analytics access logs reveal any access events from other tenant organizations during the disclosure period.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

No user action required as Google has automatically patched the vulnerability in version 1-16-0-apigee-3. Organizations should verify their Apigee-X instance is running the patched version and review analytics access logs for any anomalous cross-tenant activity around the disclosure period.

Recommended fix High confidence

1-16-0-apigee-3

  1. No user action is required. Google has automatically patched this vulnerability in version 1-16-0-apigee-3.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13292 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13292 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data