CVE-2026-4764
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 the playbook import functionality in Dialogflow CX on Google Cloud Platform allows an authenticated user with specific roles to escalate privileges and potentially take over a GCP project using a maliciously crafted playbook import. This vulnerability was patched on 15 March 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 confidenceA missing authorization check in Dialogflow CX's playbook import functionality allows authenticated users with specific roles to import maliciously crafted playbooks that escalate privileges and potentially enable full GCP project takeover.
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
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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.
-
Identify Dialogflow CX usage in your GCP projectRun: gcloud dialogflow cx agents list --location=--all-regions 2>/dev/null or check Resource Manager for dialogflow.googleapis.com usageAffected if No Dialogflow CX agents exist - the vulnerability does not apply
-
Locate Cloud Audit Logs for Dialogflow CXIn GCP Console, navigate to Logging > Logs Explorer and filter: resource.type="dialogflow.googleapis.com/Agent" AND protoPayload.methodName="google.cloud.dialogflow.cx.v3.Playbooks.ImportPlaybook"Affected if No such logs exist and you use Dialogflow CX - you cannot verify exploitation history
-
Search for playbook imports before the patch dateIn Logs Explorer, add time range: 2026-01-01 to 2026-03-14 (prior to patch on March 15, 2026) and filter for ImportPlaybook or CreatePlaybook operationsAffected if Any playbook import operations occurred in this timeframe require further investigation
-
Identify actors who performed playbook importsReview log entries for protoPayload.authenticationInfo.principalEmail and protoPayload.requestMetadata.callerIp to list all users who imported playbooksAffected if Unexpected users or service accounts imported playbooks during the vulnerable period
-
Correlate importing users with their IAM rolesRun: gcloud projects get-iam-policy $PROJECT_ID --flatten="bindings[].members" --filter="bindings.role:roles/dialogflow.cx.*" to see who had Dialogflow CX rolesAffected if Users who imported playbooks lacked explicit playbook import permissions or have overly broad Dialogflow CX roles
You are affected if Dialogflow CX was in use and any playbook import operations occurred in audit logs between early 2026 and March 14, 2026 by users without proper authorization.
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.
From vendor dataNo customer action required; Google patched this vulnerability server-side on 15 March 2026. Verify via GCP audit logs that no unauthorized playbook imports occurred prior to the patch date.
- Consultation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4764 — 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-4764 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