# CVE-2026-79483: SQL injection in n/a

> Unauthenticated attackers can inject NoSQL operators to bypass authorization and access all users' chat history titles.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 31 Aug 2026
- **Updated:** 1 Sep 2026
- **Also known as:** GHSA-5ph8-357j-4hx6

## What is CVE-2026-79483?

CVE-2026-79483 is a medium-severity SQL injection vulnerability in n/a, published on 31 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FastGPT Community Edition 4.10.0 through 4.14.0 are vulnerable to a NoSQL injection in the POST /api/core/chat/getHistories endpoint. An unauthenticated attacker can inject malicious NoSQL operators via crafted JSON payloads to bypass authorization checks, resulting in unauthorized access to chat history titles of all users across the platform.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

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


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

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

## Is CVE-2026-79483 being exploited?

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

Public exploit code:

- FastGPT Community Edition NoSQL Injection PoC (CVE-2026-79483) (github_poc): https://github.com/ExploreIO/CVE-2026-79483-FastGPT-NoSQL-Injection

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79483 is a medium-severity SQL injection vulnerability in n/a, published on 31 Aug 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-79483 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-79483/ (Markdown: https://insights.sbomify.com/CVE-2026-79483/index.md)
```

## Sources

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

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