# CVE-2026-79314: Missing authorization in n/a

> Authenticated users can modify other users' proxy configurations due to missing ownership checks, allowing unauthorized data modification.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-xr6g-3g96-fmgq

## What is CVE-2026-79314?

CVE-2026-79314 is a high-severity missing authorization vulnerability in n/a, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A horizontal privilege escalation vulnerability exists in x-ui 0.3.2. An authenticated user can modify the inbound proxy configurations of other users, including remark, port, protocol, settings, enabled state, expiry time and traffic quota, by submitting a request referencing the target resource identifier. The update path fails to verify that the target resource belongs to the requesting session user, allowing unauthorized cross-user modification of data.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-79314 being exploited?

There is no known exploitation of CVE-2026-79314 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79314 is a high-severity missing authorization vulnerability in n/a, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-79314 in the wild and no public exploit code.

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

## Sources

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

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