# CVE-2026-11346: Server-Side Request Forgery (SSRF) allowing Internal Network Probing in linqi

> An authenticated attacker can exploit SSRF in linqi to probe internal network ports and map internal infrastructure by observing HTTP response variations.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/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:** 5 Jun 2026
- **Updated:** 5 Jun 2026
- **Also known as:** GHSA-c7cw-qcqw-c783

## What is CVE-2026-11346?

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

### Official description

A Server-Side Request Forgery (SSRF) vulnerability in the custom process creation feature of linqi allows an authenticated attacker to probe internal network components. By crafting a specific process containing an HTTP Request component, an attacker can force the server to send arbitrary HTTP requests. By observing the varying application responses (Success, Failed, or 504 Gateway Time-out), the attacker can determine the status of internal ports, leading to internal network reconnaissance.

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

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


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

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

## Is CVE-2026-11346 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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