gcdRadar
archive/Patch now/AIR-2026-0002
closedclosed 5 Jan 2026Patch now2 Disclosed vulnerabilityAI

CVE-2025-67732: API Key Exposure Vulnerability in Dify

Dify

An information disclosure vulnerability in Dify prior to version 1.11.0 exposed API keys in plaintext to frontend users. The issue allowed non-administrator users to view and reuse keys, leading to unauthorized third-party service access.

disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why

CVSS
8.4
EPSS
<0.01 · top 71% · 2026-11-13
fix status
Fix status unknown
first report
5 Jan 2026
last update
5 Jan 2026

Timeline · 1

  1. 5 Jan 2026CVE-2025-67732: Dify is an open-source LLM app development platform.

Sources · 1

Advisories and databases

  1. 2026-01-05
    CVE-2025-67732: Dify is an open-source LLM app development platform.
    NVD · nvd.nist.gov/vuln/detail/CVE-2025-67732

Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.

Classification

AI role
Attack on AI
categories
Infrastructure vulnerabilityData leak
severity
2 · Disclosed vulnerability
fix status
Fix status unknown
targets
Framework / tooling
mitre atlas
no technique for these categories
dates
happened 5 Jan 2026 · first reported 5 Jan 2026
origin
NVD
Vulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
record
confidence 0.95 · created 2026-10-18 06:33Z · updated 2026-10-18 06:33Z

Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned

Copy a brief

This record as a short Markdown brief, for a ticket, a chat or a coding agent.

the brief as text
# CVE-2025-67732: API Key Exposure Vulnerability in Dify

https://gcdradar.vercel.app/incidents/cve-2025-67732-api-key-exposure-vulnerability-in-dify · AIR-2026-0002 · closed 2026-01-05

- Lane: Patch now
- Severity: 2 (Disclosed vulnerability)
- Fix status: Fix status unknown
- First reported: 2026-01-05
- AI role: Attack on AI
- Products: Dify
- CVE ids: CVE-2025-67732
- CVSS: 8.4

## Summary

An information disclosure vulnerability in Dify prior to version 1.11.0 exposed API keys in plaintext to frontend users. The issue allowed non-administrator users to view and reuse keys, leading to unauthorized third-party service access.

## What to do

No action recorded; read the sources below and the vendor's advisory.

## Latest updates

- 2026-01-05: CVE-2025-67732: Dify is an open-source LLM app development platform. (https://nvd.nist.gov/vuln/detail/CVE-2025-67732)

## Sources

- 2026-01-05 NVD: CVE-2025-67732: Dify is an open-source LLM app development platform. https://nvd.nist.gov/vuln/detail/CVE-2025-67732

Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.

Related

  1. closed9.1
    Dify Dify Authorization Bypass Leads to Tenant Trace Configuration Exposure

    Patch now · Disclosed · since 18 May 2026 · CVE-2026-41947

    AI
  2. closed8.2
    Dify CVE-2026-41949: Dify authorization bypass in file preview endpoint

    Patch now · Disclosed · since 18 May 2026 · CVE-2026-41949

    AI
  3. closed6.5
    Dify CVE-2026-41950: Authorization bypass in Dify allows unauthorized file access

    Patch now · Disclosed · since 5 May 2026 · CVE-2026-41950

    AI
  4. closed6.0
    Dify CVE-2025-59422: Broken access control vulnerability in Dify exposes chat messages

    Patch now · Disclosed · since 25 Sep 2025 · CVE-2025-59422

    AI
  5. closed7.1
    MCP SDKs CVE-2026-25536: Model Context Protocol SDK cross-client data leak

    Patch now · Disclosed · since 4 Feb 2026 · CVE-2026-25536

    AI
  6. closed8.7
    AnythingLLM CVE-2026-24477: AnythingLLM API Key Exposure Vulnerability

    Patch now · Disclosed · since 27 Jan 2026 · CVE-2026-24477

    AI