# CVE-2026-82838: Default webserver configuration with incorrect CSP

> Attackers can execute JavaScript via uploaded SVG files due to missing Content Security Policy in the default Docker image.

- **Severity:** Medium 6.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-38wh-hqvm-xgfc

## What is CVE-2026-82838?

CVE-2026-82838 is a medium-severity cross-site scripting vulnerability in pretix venueless, published on 31 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The default docker image shipped for Venueless did not properly ensure that uploaded SVG files could not be delivered with executable JavaScript content. A valid Content Security Policy is now set.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

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


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

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

## Is CVE-2026-82838 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82838 is a medium-severity cross-site scripting vulnerability in pretix venueless, published on 31 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-82838 in the wild and no public exploit code.

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

## Sources

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

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