Security readout for executives and security teams
Plain-English summary
Dify versions before 1.9.0 can reveal whether an email address is registered through differing API responses. This does not directly compromise accounts, but it can support phishing, credential attacks, and privacy exposure. Organizations running public or partner-facing Dify instances should prioritize upgrading.
Executive priority
Treat as a near-term privacy and abuse-prevention fix, not an emergency breach indicator. Upgrade affected Dify instances during the next available maintenance window, sooner for public-facing or high-profile environments.
Technical view
CVE-2026-28288 is a CWE-204 observable response discrepancy in langgenius Dify before 1.9.0. Unauthenticated network access can compare API behavior for existing versus non-existent accounts, enabling email enumeration. CVSS v4.0 is 5.5, medium severity, with low attack complexity and limited confidentiality impact.
Likely exposure
Exposure is most relevant for internet-accessible Dify deployments, shared enterprise instances, or environments where registered user email addresses are sensitive. Self-hosted Dify versions earlier than 1.9.0 are affected according to the advisory data.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked as KEV. The issue is easy to attempt remotely because it requires no privileges or user interaction, but the documented impact is limited to account/email enumeration.
Researcher notes
Sources identify response differences between existing and non-existent accounts, but do not provide broader exploitation evidence. Validate only through safe version checks and vendor advisory review; avoid probing production accounts in ways that could expose personal data.
Mitigation direction
- Upgrade Dify to version 1.9.0 or later.
- Review the GitHub advisory for any updated vendor guidance.
- Reduce public exposure of Dify APIs where business requirements allow.
- Monitor authentication and account-related endpoints for unusual enumeration patterns.
Validation and detection
- Inventory Dify deployments and confirm running versions.
- Flag any Dify instance below 1.9.0 as affected.
- Confirm upgrade completion to 1.9.0 or later.
- Review logs for repeated account-checking behavior from common sources.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-204: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-28288 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
5.5MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/langgenius/dify/security/advisories/GHSA-9qpf-wcv3-w3qxCVE reference · x_refsource_CONFIRM
- https://github.com/langgenius/dify/issues/24323CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Observable Response Discrepancy
Observable Response Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.