# CVE-2026-86273: projeto-siga HTML-to-PDF Endpoint ExUtilController.java DownloadExterno.getUrl server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the HTML-to-PDF endpoint to access internal resources.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/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:** Not needed
- **Fix available:** No
- **Published:** 7 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-pcw6-8cpc-9hvx

## What is CVE-2026-86273?

CVE-2026-86273 is a medium-severity server-side request forgery vulnerability in projeto-siga siga, published on 7 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weakness has been identified in projeto-siga siga up to 11.1.1. Affected by this issue is the function DownloadExterno.getUrl of the file sigaex/src/main/java/br/gov/jfrj/siga/vraptor/ExUtilController.java of the component HTML-to-PDF Endpoint. This manipulation of the argument html causes server-side request forgery. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

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

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


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

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

## Is CVE-2026-86273 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86273 is a medium-severity server-side request forgery vulnerability in projeto-siga siga, published on 7 Sep 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-86273 exists.

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

## Sources

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

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