# CVE-2026-50879: linx-server has an issue in the uploadPostHandler component that allows attackers to cause a Denial of Service (DoS) via a crafted POST request

> Attackers can cause a Denial of Service in linx-server by sending a crafted POST request to the upload handler.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-g743-m6x3-v6wm, GO-2026-6297

## What is CVE-2026-50879?

CVE-2026-50879 is a high-severity denial of service vulnerability in n/a, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in the uploadPostHandler component of Andrei Marcu linx-server v2.3.8 allows attackers to cause a Denial of Service (DoS) via a crafted POST request.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

3 open source packages ship an affected version, including github.com/andreimarcu/linx-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/andreimarcu/linx-server` | Go | All versions | None |
| `github.com/andreimarcu/linx-server` | Go | All versions to 2.3.8 | None |
| `github.com/andreimarcu/linx-server` | Go | All versions to 2.3.8 | None |

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

Upgrade to a fixed version.

## Is CVE-2026-50879 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50879 is a high-severity denial of service vulnerability in n/a, published on 15 Jun 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-50879 exists.

Affected packages and fixed versions:
- github.com/andreimarcu/linx-server (Go): affected all versions; no fix listed
- github.com/andreimarcu/linx-server (Go): affected all versions up to 2.3.8; no fix listed
- github.com/andreimarcu/linx-server (Go): affected all versions up to 2.3.8; no fix listed

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-50879/ (Markdown: https://insights.sbomify.com/CVE-2026-50879/index.md)
```

## Sources

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

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