PipesHub before 0.10.0 SSRF via Image URLs in Indexed Documents
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 0.10.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
- First seen by cve.now
Affected versions
- pipeshub-ai pipeshub-ai
fixed in 0.10.0
References 7
GitHub · pipeshub-ai/pipeshub-ai
GitHub · hyderpwn/CVE-pipeshub
Questions about CVE-2026-119712
What does this mean?
When PipesHub indexes a document with Markdown or HTML image links, it fetches those image URLs. A document author can point them at loopback, private-network, or cloud metadata addresses, so the server makes requests to internal services and can reach the hosting account's instance credentials.Source: github.com
Am I affected, and how do I check?
Versions from 0.1.0 up to but not including 0.10.0 are in the affected range. To check a deployment, look up the installed PipesHub version; the bug applies only when indexed documents contain Markdown or HTML with image URLs.Source: github.com
What should I do about it?
Upgrade to PipesHub 0.10.0 or later. The fixed release checks each image URL against the blocked-host policy before fetching it, including any redirects.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data