Evidence · DiggingBeagle record
OmniRoute patch: route specialist executors through centralized egress guard
Source diff introducing per-hop redirect checks to specialized provider executors.
- Published
- Nov 14, 2026
- Source role
- patch commit artifact
Evidence record
Source diff introducing per-hop redirect checks to specialized provider executors.
Claim-level citations (2)
- supportsProvider-specific execution paths bypassed a centralized destination and redirect guard: OmniRoute has several model-provider executors with specialized request and retry logic. The patch routes nine of these paths through a shared dispatcher that validates destinations and redirect hops rather than allowing self-dispatched fetches. An input endpoint or redirect can cross from a configured provider call to a private destination, while authorization headers could be forwarded under some request configurations. The code change confirms inconsistent enforcement, not a proved secret leak across all nine providers.
OmniRoute commit 5dde987, specialist provider dispatcher changes and redirect enforcement
- supportsProvider-specific execution paths bypassed a centralized destination and redirect guard: Which provider credentials or internal addresses are exposed depends on each executor's actual URL controls, HTTP behavior and deployment egress. The finding should not be combined with the caller-selected SearXNG URL path, which is a different entry point. The evidence is bounded by the cited source and test setting. Broader incidence, other environments, and actual production consequences are not established merely by these observations.
Primary disclosure: results, scope and limitations