PipesHub 0.3.0 before 0.10.0 Connector Deletion via Crawling-Manager Schedule Route
PipesHub 0.3.0 through 0.9.1 lets a caller holding only the crawl:write scope permanently delete a connector and its indexed records and embeddings. Fixed in 0.10.0.
- 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? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
PipesHub is affected: an authenticated user who holds only the crawl:write permission can delete connectors, bypassing the normal connector-deletion permission and lock checks. Deleting a connector also removes its associated record embeddings, causing loss of indexed data.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
PipesHub 0.3.0 before 0.10.0 contains an event type injection vulnerability that allows authenticated users with only the crawl:write scope to delete connectors by injecting into the :connector path segment. Attackers can send a :connector value like web.delete to the schedule route, bypassing connector:delete and lock checks to remove connector instances and purge record embeddings.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- pipeshub-ai pipeshub-ai
From 0.3.0 · fixed in 0.10.0
References 6
Questions about CVE-2026-119710
What does this mean?
A caller with only the crawl:write scope can permanently destroy a connector and its indexed records and embeddings. This works without the connector:delete scope and bypasses the connector-locked guard.Source: github.com
Am I affected, and how do I check?
Versions 0.3.0 up to and including 0.9.1 are affected. On 0.9.1 and earlier, the connectorName field of POST /connectors/:id/resync also reaches the same event consumer. The vulnerable route is the crawling manager schedule endpoint, which requires only the crawl:write scope, so check the installed version and which accounts hold crawl:write.Source: github.com
What should I do about it?
Upgrade to PipesHub 0.10.0 or later. The fix takes the connector event type from the stored connector instance rather than from the :connector path segment.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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data