# CVE-2025-67732: Dify Vulnerable to Plaintext API Key Exposure via Model Provider Configuration Endpoint

> Non-administrator users can view plaintext API keys via the model provider configuration endpoint, enabling unauthorized access to third-party services.

- **Severity:** High 8.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jan 2026
- **Updated:** 6 Jan 2026
- **Also known as:** GHSA-phpv-94hg-fv9g

## What is CVE-2025-67732?

CVE-2025-67732 is a high-severity vulnerability in langgenius dify, published on 5 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Dify is an open-source LLM app development platform. Prior to version 1.11.0, the API key is exposed in plaintext to the frontend, allowing non-administrator users to view and reuse it. This can lead to unauthorized access to third-party services, potentially consuming limited quotas. Version 1.11.0 fixes the issue.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Dify Dify.

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

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

## Is CVE-2025-67732 being exploited?

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

## Other vulnerabilities in langgenius dify

- [CVE-2026-41947](https://insights.sbomify.com/CVE-2026-41947/): Dify < 1.14.2 Authorization Bypass via Trace Configuration Endpoints (critical 9.3)
- [CVE-2026-41948](https://insights.sbomify.com/CVE-2026-41948/): Dify v1.14.1 Path Traversal via Plugin Daemon Internal API Access (critical 9.3)
- [CVE-2025-0185](https://insights.sbomify.com/CVE-2025-0185/): Pandas Query Injection in langgenius/dify (high 8.8)
- [CVE-2026-61461](https://insights.sbomify.com/CVE-2026-61461/): Dify < 1.16.0-rc1 SQL Injection via MyScale Vector Store search_by_full_text (high 8.7)
- [CVE-2026-41949](https://insights.sbomify.com/CVE-2026-41949/): Dify < 1.14.2 Authorization Bypass via File Preview Endpoint (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-67732 is a high-severity vulnerability in langgenius dify, published on 5 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67732 in the wild and no public exploit code.

Affected product: langgenius dify. 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-67732/ (Markdown: https://insights.sbomify.com/CVE-2025-67732/index.md)
```

## Sources

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

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