# CVE-2026-56769: Huly Platform - Server-Side Request Forgery via /import Endpoint

> Authenticated users can exploit SSRF in the /import endpoint to access internal services and exfiltrate data.

- **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:** 25 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-wg7f-c2g2-5gwm

## What is CVE-2026-56769?

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

### Official description

Huly Platform through 0.7.423, fixed in commit 68cbf8a contains an authenticated server-side request forgery vulnerability in the /import endpoint of front pod that allows workspace users to make arbitrary server requests. Attackers can exploit this by supplying malicious URLs to fetch internal services, exfiltrate responses, and replay credentials against backend systems.

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

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


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

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

## Is CVE-2026-56769 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56769 is a medium-severity server-side request forgery vulnerability in hcengineering platform, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56769 exists.

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

## Sources

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

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