# CVE-2026-120492: Chainlit 2.12.0 SSRF via Semicolon Path Segment in MCP allowed_urls


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 2 Nov 2026
- **Updated:** 7 Nov 2026
- **Also known as:** GHSA-xhx7-9vjr-p2h8

## What is CVE-2026-120492?

CVE-2026-120492 is a medium-severity vulnerability in Chainlit, published on 2 Nov 2026. 

### Official description

Chainlit 2.12.0 contains a server-side request forgery vulnerability that allows unauthenticated attackers to bypass path-scoped MCP allowed_urls entries because validate_mcp_url does not reject the semicolon character. Attackers can submit MCP URLs with '..;' segments to the /mcp endpoint, causing requests to paths outside the operator's grant on origins that strip semicolon path parameters.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-120492?


## How do I fix CVE-2026-120492?

Upgrade to a fixed version.

## Is CVE-2026-120492 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120492 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120492 and fix it if it is affected.

What it is: CVE-2026-120492 is a medium-severity vulnerability in Chainlit, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120492 exists.

Affected product: Chainlit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120492/ (Markdown: https://insights.sbomify.com/CVE-2026-120492/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120492
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120492
- OSV: https://osv.dev/vulnerability/CVE-2026-120492

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120492/
Summaries are generated and may contain mistakes; the official description above is the record.
