CVE-2025-67732 langgenius CVE debrief

Who should care

Defenders of Dify instances, administrators, and users of third-party services should assess exposure and prioritize remediation. They should verify the Dify instance version, check for API key exposure, and monitor for unauthorized access to third-party services. Additionally, they should review compensating controls for exposed systems and track exceptions, retest remediated assets, and close the item only after evidence is documented.

Why it matters

CVE-2025-67732 exposes Dify API keys, risking unauthorized third-party service access. Defenders of Dify instances and administrators must verify exposure, prioritize remediation, and monitor for unauthorized access.

• Potential unauthorized access to third-party services
• Consumption of limited quotas by non-administrator users
• Need for verification of Dify instance version and API key exposure
• Prioritization of remediation to prevent unauthorized access

Technical summary

Dify open-source LLM app development platform exposed API key in plaintext to frontend before version 1.11.0, allowing non-administrator users to view and reuse it. This vulnerability risks unauthorized access to third-party services and consumption of limited quotas. Defenders should prioritize verifying exposure and remediating vulnerable Dify instances by upgrading to version 1.11.0 or later and monitoring for unauthorized access. The vulnerability affects Dify instances prior to version 1.11.0, and defenders should review the official CVE Program record and NVD detail page for further information.

Defensive priority

Defenders should prioritize verifying exposure and remediating vulnerable Dify instances.

Recommended defensive actions

• Verify Dify instance version and check for API key exposure
• Upgrade to version 1.11.0 or later
• Monitor for unauthorized access to third-party services
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the API key exposure in Dify before version 1.11.0. Evidence is limited to public sources, and defenders should verify the vulnerability and its impact on their instances. The CVE record was published on 2026-01-05T22:15:51.837Z and has not been modified since then. Defenders should review the official CVE Program record and NVD detail page for further information.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.