CVE-2026-8934
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 · uneditedA Missing Authorization vulnerability in a GraphQL private API operation of the Google App Engine section of the Cloud Console allows an unauthenticated remote attacker to leak sensitive App Engine request logs from other projects using a specially crafted request. This vulnerability was patched on 7 April 2026, and no customer action is needed.
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 · high confidenceThis is a Missing Authorization vulnerability in the GraphQL private API for Google App Engine within Cloud Console. An unauthenticated attacker can send specially crafted requests to leak sensitive App Engine request logs from other projects, bypassing proper access controls on the private API operation.
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
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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 checksWork through these to decide whether this CVE applies to you.
-
Review Cloud Audit Logs for unauthorized App Engine GraphQL API accessExamine Google Cloud Cloud Logging for entries involving the App Engine private GraphQL API. Filter for API calls from unauthenticated or unexpected principals accessing log retrieval operations.Affected if Logs show API calls to the App Engine GraphQL private endpoint from unauthenticated sources or cross-project principals that should not have access
-
Check IAM policy for App Engine Log Viewer permissionsReview IAM policies on your Google Cloud projects to identify which principals have roles like 'App Engine Log Viewer' or custom roles with log access. Use 'gcloud projects get-iam-policy' or the Cloud Console IAM page.Affected if Users or service accounts outside your project organization have been granted log access permissions unexpectedly
-
Verify cross-project log access attempts in VPC Service ControlsIf VPC Service Controls are enabled, review perimeter logs for attempts to access App Engine logs from outside the trusted perimeter using the private API.Affected if VPC SC perimeter logs show successful cross-perimeter access to App Engine log resources that should be restricted
-
Search for anomalous App Engine log export operationsReview Cloud Logging filters for 'appengine.googleapis.com' resource types with log read operations. Look for patterns indicating bulk log exfiltration or queries for logs outside the expected time range or project scope.Affected if Log queries retrieve App Engine request logs from projects the principal does not own or have legitimate access to
A user is likely affected if Cloud Audit Logs or IAM configurations show unauthorized cross-project access to App Engine request logs via the private GraphQL API since before the 7 April 2026 patch date.
Generated from the published advisory. Verify against your own configuration.
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 · scopedNo customer action required; Google patched this vulnerability on 7 April 2026. Organizations may optionally conduct a review to verify the fix and assess for similar authorization gaps in their Google Cloud configurations.
- No customer action required. Google has already patched this vulnerability server-side.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing1.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8934 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8934 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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