# CVE-2026-91079: Huly Platform through 0.7.426 SSRF via Print Service

> Authenticated users can exploit missing hostname validation in the print service to access internal network resources and metadata services.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:L/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:** 14 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-prm2-rg4g-w438

## What is CVE-2026-91079?

CVE-2026-91079 is a medium-severity server-side request forgery vulnerability in hcengineering platform, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Huly Platform through 0.7.426 contains a server-side request forgery vulnerability in the print service due to missing hostname allowlist validation. Authenticated workspace members can supply arbitrary URLs to the print endpoint, which Puppeteer renders and returns as downloadable PDFs or images, enabling access to internal metadata services and network hosts.

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

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


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

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

## Is CVE-2026-91079 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91079 is a medium-severity server-side request forgery vulnerability in hcengineering platform, published on 14 Sep 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-91079 in the wild and no public exploit code.

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

## Sources

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

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