The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsLearn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learningUpgrade chainlit to version 2.12.0 or higher.
chainlit is a Build Conversational AI.
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the connect_mcp handler in backend/chainlit/server.py. When MCP is enabled, an unauthenticated attacker who can open a session can send POST /mcp requests using the SSE or streamable-HTTP transport with an arbitrary URL and attacker-controlled headers, causing the Chainlit server to make outbound requests to internal services or cloud metadata endpoints. Although the responses are not returned to the attacker, forged headers can let them trigger state-changing requests to internal APIs.
Notes
features.mcp.enabled = true in .chainlit/config.toml; MCP has been disabled by default since v2.7.0, so deployments retaining that default are not exposed.Workarounds
features.mcp.enabled = false in .chainlit/config.toml to prevent exploitation through the /mcp endpoint./mcp requires an authenticated session; this removes the unauthenticated attack path but does not prevent SSRF by authenticated users.