Loading story…
A high-severity vulnerability, tracked as CVE-2025-67732, was discovered in the open-source LLM app development platform Dify. The flaw allowed API keys to be exposed in plaintext through the model provider configuration endpoint, making them accessible to non-administrator users via the frontend. This exposure could enable unauthorized individuals to view and reuse the API keys, potentially granting them access to third-party services and consuming limited quotas. The issue was addressed and fixed in Dify version 1.11.0, mitigating the risk of unauthorized access.
Security advisories highlighted the remote exploitability of this vulnerability, emphasizing the risk of API key leakage and subsequent misuse. The vulnerability was assigned a CVSS 4.0 score of 8.4, reflecting its high severity. Organizations using Dify are urged to update to version 1.11.0 or later to prevent exploitation and protect sensitive API credentials from exposure.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
2 events from the most recent confirmed update back to the earliest known activity.
CVE-2025-67732 was published as a high-severity vulnerability affecting Dify versions prior to 1.11.0. The disclosure described remote exploitation risks from plaintext API key exposure and potential unauthorized use of third-party services.
Dify fixed a high-severity flaw that exposed model provider API keys in plaintext to non-administrator users via the Model Provider Configuration endpoint. The issue was resolved in version 1.11.0, and users were advised to update and rotate any exposed keys.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
2 references tracked. Mallory keeps watching after this page renders.
securityonline.info
Open sourcecvefeed.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Researchers disclosed four vulnerabilities in the open-source AI application platform **Dify** that could let attackers silently access sensitive customer data, including private AI chat histories and uploaded files. The issues, collectively named **DifyTap** by Zafran Security, affected tracing configuration, the internal Plugin Daemon API, document preview authorization, and cross-file user access. Two of the flaws were rated critical, and some attack paths were unauthenticated, creating cross-tenant exposure risks in Dify's multi-tenant cloud service. The vulnerabilities could enable persistent interception and exfiltration of AI conversations, abuse of Dify's internal plugin services, preview of uploaded documents from other tenants, and access to files belonging to other users in the same tenant. Zafran said Dify is widely deployed, citing more than 10 million API image pulls and tens of thousands of internet-facing instances. Dify patched three issues in version **1.14.2**, while **`CVE-2026-41948`** remained pending at disclosure, with a fix merged on GitHub and additional mitigation available through targeted WAF rules; researchers also noted Dify's file parsing stack included vulnerable **PDFium** code affected by **`CVE-2024-5846`**.
Jun 29, 2026
Rich Source **DMS+ (Non-Mobile)** contains a critical hard-coded credentials flaw tracked as **`CVE-2026-18452`** that allows **unauthenticated remote attackers** to use a fixed embedded API key to gain administrative control over affected DMS+ instances and the devices they manage. The vulnerability affects **versions 5.63 and earlier** and is classified as **CWE-798: Use of Hard-coded Credentials**. The issue carries a **CVSS v3.1 score of 9.8** with impact to confidentiality, integrity, and availability, and public reporting said exploitation requires no authentication and low attack complexity. **Rich Source** addressed the flaw in **version 5.64**, while **TWCERT/CC** published an advisory; no active exploitation had been reported at the time of publication.
Jul 31, 2026
A high-severity vulnerability tracked as **CVE-2026-62327** affects decolua's **9Router** through version **0.4.41**, allowing remote attackers to retrieve plaintext API keys for all connected AI provider accounts without authentication. The flaw stems from missing authentication middleware on the Next.js API route `/api/usage/stats`, enabling a single unauthenticated request to disclose sensitive account data. In addition to API keys, the exposed response can include token counts, cost breakdowns, and request metadata, creating risks of unauthorized use of linked AI services, billing fraud, and quota exhaustion. The issue is classified as an information disclosure vulnerability tied to **CWE-306** and **CWE-522**, with a **CVSS 3.1 score** reflecting high impact from network-accessible exploitation requiring no privileges or user interaction.
Jul 14, 2026