# CVE-2025-52186: Server-side request forgery in n/a

> Attackers can exploit an SSRF vulnerability in the game export API to force the server to send requests to arbitrary internal or external URLs.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-85hq-hqhm-3jf2

## What is CVE-2025-52186?

CVE-2025-52186 is a medium-severity server-side request forgery vulnerability in n/a, published on 13 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Lichess lila before commit 11b4c0fb00f0ffd823246f839627005459c8f05c (2025-06-02) contains a Server-Side Request Forgery (SSRF) vulnerability in the game export API. The players parameter is passed directly to an internal HTTP client without validation, allowing remote attackers to force the server to send HTTP requests to arbitrary URLs

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

## Which versions are affected by CVE-2025-52186?

It affects 1 product.


Products: Lichess Lila.

## How do I fix CVE-2025-52186?

No fix has been published for CVE-2025-52186 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-52186 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-35208](https://insights.sbomify.com/CVE-2026-35208/): lichess.org has an Unsanitized Stream Title Injection on /streamer (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52186 and fix it if it is affected.

What it is: CVE-2025-52186 is a medium-severity server-side request forgery vulnerability in n/a, published on 13 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52186 exists.

Affected product: n/a. 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-2025-52186/ (Markdown: https://insights.sbomify.com/CVE-2025-52186/index.md)
```

## Sources

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

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