CVE-2025-12952
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 privilege escalation vulnerability exists in Google Cloud's Dialogflow CX. Dialogflow agent developers with Webhook editor permission are able to configure Webhooks using Dialogflow service agent access token authentication. This allows the attacker to escalate their privileges from agent-level to project-level, granting them unauthorized access to manage resources in services associated with the project, leading to unexpected costs and resource depletion for the producer project. A fix was applied on the server side to protect from this vulnerability in February 2025. No customer action is required.
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 privilege escalation vulnerability in Google Cloud's Dialogflow CX allows developers with Webhook editor permission to configure Webhooks using Dialogflow service agent access tokens. This enables escalation from agent-level to project-level permissions, granting unauthorized access to project resources and potentially causing unexpected costs and resource depletion.
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: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.
-
Identify Dialogflow CX agents in your projectRun: gcloud alpha dialogflow cx agents list --location=--all-regions 2>/dev/null || gcloud dialogflow cx agents list 2>/dev/null. If no agents exist, you are not affected.Affected if You have any Dialogflow CX agents deployed in your Google Cloud project(s)
-
Check for configured webhooksFor each agent identified, run: gcloud alpha dialogflow cx webhooks list --agent=AGENT_NAME --location=LOCATION. Alternative: inspect agent configuration files or deployment templates for webhook definitions.Affected if Webhooks are defined and attached to your Dialogflow CX agents
-
Inspect webhook configuration for service agent tokensRun: gcloud alpha dialogflow cx webhooks describe WEBHOOK_NAME --agent=AGENT_NAME --location=LOCATION. Look for any field containing 'serviceAgent' or 'dialogflow.serviceagent' in credential-related parameters (such as headers, authentication, or token fields).Affected if Webhook configuration references Dialogflow service agent credentials or access tokens
-
Review audit logs for webhook modificationsRun: gcloud logging read 'protoPayload.methodName="dialogflowcx.webhooks.*" AND protoPayload.authenticationInfo.principalEmail="*.gserviceaccount.com"' --limit=50 --order-by="timestamp desc". Check if webhooks were created or modified using service agent accounts before February 2025.Affected if Audit logs show webhook operations performed by Dialogflow service agent accounts prior to February 2025
If you use Dialogflow CX with webhooks that were configured using Dialogflow service agent access tokens before Google's February 2025 server-side fix, your environment was potentially affected by this privilege escalation vulnerability.
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 applied a server-side fix in February 2025 to protect against this vulnerability.
- No customer action required. Google has applied a fix on the server side in February 2025 to protect against this vulnerability.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing0.5 h
- Review / QA0.5 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-2025-12952 — 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-2025-12952 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