# CVE-2026-52100: Cross-site request forgery in n/a

> A CSRF vulnerability in linux-server allows remote attackers to execute arbitrary code via the uploadPutHandler function.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-977p-rxc5-4hrg

## What is CVE-2026-52100?

CVE-2026-52100 is a high-severity vulnerability in n/a, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cross Site Request Forgery vulnerability in andreimarcu linux-server v.1.0 through v.2.3.8 allows a remote attacker to execute arbitrary code via the uploadPutHandler function

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-52100 being exploited?

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

Public exploit code:

- Public disclosure for CVE-2026-52100 (CSRF) & CVE-2026-52101 (SSRF) in linx-server. MITRE assigned the CVEs; this repo provides a public reference and helps affected users understand the risk. (github_poc): https://github.com/nk7667/-linx-server-vulnerability-report

## Fix prompt for AI coding agents

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

What it is: CVE-2026-52100 is a high-severity vulnerability in n/a, published on 14 Jul 2026. 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-2026-52100 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-2026-52100/ (Markdown: https://insights.sbomify.com/CVE-2026-52100/index.md)
```

## Sources

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

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