# CVE-2026-82044: UTMStack < 11.2.16 Server-Side Request Forgery via downloadPdf

> Authenticated attackers can exploit an unvalidated URL parameter to force the server to fetch internal resources, exposing sensitive data in generated PDFs.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **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:** 2 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-hg4r-wjvj-4cww

## What is CVE-2026-82044?

CVE-2026-82044 is a medium-severity server-side request forgery vulnerability in UTMStack, published on 2 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

UTMStack before 11.2.16 contains a server-side request forgery vulnerability that allows authenticated attackers to make the server request arbitrary internal resources by supplying an unvalidated url parameter to the PdfService.downloadPdf() method exposed via GET /api/generate-pdf-report. Attackers can leverage this to force the web-pdf microservice to fetch internal backend endpoints, the OpenSearch cluster, or the cloud instance-metadata service, exposing sensitive internal data rendered into the returned PDF.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-82044 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82044 is a medium-severity server-side request forgery vulnerability in UTMStack, published on 2 Oct 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-82044 in the wild and no public exploit code.

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

## Sources

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

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