CVE-2026-41948

This vulnerability lets an attacker “trick” Dify into looking at the wrong internal web address, by putting special characters in the URL path. If successful, they may be able to reach internal Dify functions that are not meant to be available through that normal route—like hidden/debug-style features or parts of other tenants.
Think of it like giving someone the ability to file paperwork using a misleading address, so it gets routed past your intended office boundaries.

This matters if you run dify (Dify) version 1.14.1 or earlier and you have the Plugin Daemon / plugin-related internal API routing enabled. The findings indicate the issue can be triggered over the network with no user interaction, and it is described as not requiring authentication in the core analysis.
However, the practical risk depends on whether an attacker can reach the affected endpoints/routes in your environment (for example, whether those internal paths are exposed to users on your network or via a public interface).

This is an AMBER issue: the vulnerability is serious (it can reach internal endpoints and potentially bypass tenant boundaries), but there is no confirmed KEV listing and no clear dated reporting of real-world exploitation in the findings provided. Treat it as a high-priority patch/update because the flaw is network-reachable and requires no special user interaction once an attacker can access the relevant routes.