Approved changes feed: RSS · Atom

cpe:2.3:a:langgenius:dify:*:*:*:*:*:node.js:*:*

part: a version: * update: *

VendorLanggenius (a11e3e82-2124-53e0-86c4-d486ffc06315)
ProductDify (06d833dc-7fe4-596f-bc9e-8cb6d713e080)
Edition*
Language*
Software edition*
Target softwarenode.js
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-42138 vulnerable 2026-06-08 08:03:15.947486 Dify Vulnerable to Stored XSS via SVG-file upload
Dify is an open-source LLM app development platform. Prior to version 1.13.1, using the method POST /api/files/upload, any unauthenticated user can upload an SVG file with XSS. The method POST /v1/files/upload, which requires authentication through the application API, is also vulnerable. This issue has been patched in version 1.13.1.
Published: 2026-05-04T17:34:36.199Z
Updated: 2026-05-04T18:48:58.586Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-41950 vulnerable 2026-06-08 08:03:15.803542 Dify < 1.14.0 Authorization Bypass via File UUID
MEDIUM (6.5)
Dify before version 1.14.0 contains an authorization bypass vulnerability that allows authenticated users to read the full contents of files uploaded by other users within the same tenant by supplying an arbitrary file UUID in the files array of a chat-messages request. Attackers can exploit insufficient permission verification in the chat-messages endpoints to access files without ownership validation, bypassing workspace separation and signed URL protections to retrieve sensitive file contents through workflow processing.
Published: 2026-05-05T20:35:56.073Z
Updated: 2026-07-14T20:01:02.893Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-58747 vulnerable 2026-06-08 07:35:19.476467 Dify MCP OAuth Flow Vulnerable to XSS
Dify is an LLM application development platform. In Dify versions through 1.9.1, the MCP OAuth component is vulnerable to cross-site scripting when a victim connects to an attacker-controlled remote MCP server. The vulnerability exists in the OAuth flow implementation where the authorization_url provided by a remote MCP server is directly passed to window.open without validation or sanitization. An attacker can craft a malicious MCP server that returns a JavaScript URI (such as javascript:alert(1)) in the authorization_url field, which is then executed when the victim attempts to connect to the MCP server. This allows the attacker to execute arbitrary JavaScript in the context of the Dify application.
Published: 2025-10-17T15:48:04.980Z
Updated: 2025-10-17T15:58:42.220Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-56157 vulnerable 2026-06-08 07:33:15.531390 Details available
Default credentials in Dify thru 1.5.1. PostgreSQL username and password specified in the docker-compose.yaml file included in its source code. NOTE: the Supplier reports that the Docker configuration does not make PostgreSQL (on TCP port 5432) exposed by default in version 1.0.1 or later.
Published: 2025-12-18T00:00:00.000Z
Updated: 2026-07-05T01:27:39.511Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-43862 vulnerable 2026-06-08 07:25:10.409721 Dify Allows Unauthorized Access and Modification of APP Orchestration
HIGH (7.6)
Dify is an open-source LLM app development platform. Prior to version 0.6.12, a normal user is able to access and modify APP orchestration, even though the web UI of APP orchestration is not presented for a normal user. This access control flaw allows non-admin users to make unauthorized access and changes on the APPSs. This issue has been patched in version 0.6.12. A workaround for this vulnerability involves updating the the access control mechanisms to enforce stricter user role permissions and implementing role-based access controls (RBAC) to ensure that only users with admin privileges can access Orchestration of the APPs.
Published: 2025-04-25T15:05:32.172Z
Updated: 2025-04-25T15:54:38.110Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-43854 vulnerable 2026-06-08 07:25:10.400240 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-3467 vulnerable 2026-06-08 07:23:08.952657 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-3466 vulnerable 2026-06-08 07:23:08.952180 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-32796 vulnerable 2026-06-08 07:19:00.863502 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-32795 vulnerable 2026-06-08 07:19:00.862929 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-32790 vulnerable 2026-06-08 07:19:00.857041 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-0184 vulnerable 2026-06-08 07:00:29.887294 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-11824 vulnerable 2026-06-08 06:23:50.460336 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data
CVE:CVE-2024-10252 vulnerable 2026-06-08 06:22:03.849585 db.gcve.eu details were skipped to keep the page responsive. Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.