# CVE-2026-18682: OpenAkita File Upload API upload cross site scripting

> Remote attackers can execute arbitrary scripts via the File Upload API in OpenAkita, potentially compromising user sessions.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-2pjc-27f2-cwx3

## What is CVE-2026-18682?

CVE-2026-18682 is a low-severity cross-site scripting vulnerability in OpenAkita, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A security flaw has been discovered in OpenAkita up to 1.27.12. This vulnerability affects unknown code of the file /api/upload of the component File Upload API. The manipulation of the argument File results in cross site scripting. The attack may be performed from remote. A high complexity level is associated with this attack. It is stated that the exploitability is difficult. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-18682 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18682 is a low-severity cross-site scripting vulnerability in OpenAkita, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-18682 exists.

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

## Sources

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

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