# CVE-2026-119712: PipesHub before 0.10.0 SSRF via Image URLs in Indexed Documents


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-5r5q-7f5q-f5h2, GHSA-mp2g-r37c-fx9q

## What is CVE-2026-119712?

CVE-2026-119712 is a medium-severity vulnerability in pipeshub-ai, published on 30 Oct 2026. 

### Official description

PipesHub before 0.10.0 contains a server-side request forgery vulnerability in ImageParser._fetch_single_url that allows attackers to make the indexing service fetch internal addresses by embedding image URLs in documents. Attackers can supply Markdown or HTML via uploads, synced mailboxes, or web connectors to reach loopback, private-network, or cloud metadata endpoints, with image responses embedded into indexed content.

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

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


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

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

## Is CVE-2026-119712 being exploited?

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

Public exploit code:

- CVE-2026-119712 (CVSS 8.5 High) — PipesHub < 0.10.0 SSRF via image URLs in indexed documents (CWE-918). Verified PoC. (github_poc): https://github.com/hyderpwn/CVE-pipeshub

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119712 is a medium-severity vulnerability in pipeshub-ai, published on 30 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119712 exists.

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

## Sources

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

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