# CVE-2025-13427: Authentication Bypass in Dialogflow CX Messenger

> Unauthenticated attackers can bypass authentication to access restricted chat agent knowledge and trigger intents in Google Cloud Dialogflow CX Messenger.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2025
- **Updated:** 19 Dec 2025
- **Also known as:** GHSA-p5gx-f9rx-95rw

## What is CVE-2025-13427?

CVE-2025-13427 is a medium-severity authentication bypass vulnerability in Google Cloud Dialogflow CX Messenger, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass vulnerability in Google Cloud Dialogflow CX Messenger allowed unauthenticated users to interact with restricted chat agents, gaining access to the agents' knowledge and the ability to trigger their intents, by manipulating initialization parameters or crafting specific API requests. 

All versions after August 20th, 2025 have been updated to protect from this vulnerability. No user action is required for this.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2025-13427 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13427 is a medium-severity authentication bypass vulnerability in Google Cloud Dialogflow CX Messenger, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13427 in the wild and no public exploit code.

Affected product: Google Cloud Dialogflow CX Messenger. 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-13427/ (Markdown: https://insights.sbomify.com/CVE-2025-13427/index.md)
```

## Sources

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

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