GHSA-qqc3-94qv-7fw3 Hubuum client library (Rust): Configured custom transports may be bypassed, exposing credentials and network traffic

• crates.io hubuum_client: >= 0.3.0, < 0.6.1 → fixed in 0.6.1

Summary When an application configures hubuum_client with ClientBuilder::with_transport, several client operations still use the built-in reqwest client directly. The bypass includes password login, bearer-token validation, authentication-provider discovery, health and readiness probes, export-output downloads, and unified-search streams. Impact Applications may use a custom transport as a security boundary for network isolation, proxy enforcement, request signing, audit logging, or policy checks. Affected operations bypass those controls and make direct network requests to the configured base URL. Password login can therefore send plaintext credentials outside the intended transport, while token validation can send a bearer token outside it. Other bypassing calls can evade audit and routing policy. The issue affects custom transports introduced in 0.3.0. Applications that do not configure a custom transport are not affected by the bypass. Defense in depth The same private fix disables redirect following for built-in async and blocking clients so an authenticated request remains at the endpoint validated and constructed by the client. Applications supplying a preconfigured reqwest client continue to control its redirect policy. Remediation The proposed fix routes authentication, public discovery and probe calls, export downloads, unified-search streams, raw requests, and typed requests through the configured transport in both async and blocking clients. It preserves retry and error-body policies, documents the buffering semantics of custom transports, and surfaces built-in-client redirects as 3xx API errors. Validation Regression tests assert async and blocking routing, paths, login bodies, bearer headers, streaming bodies, retries, error handling, and redirect behavior. Formatting, Clippy with warnings denied, rustdoc warnings, the complete workspace suite, all supported feature combinations, Rust 1.88 MSRV, OpenAPI validation, and the combined library plus downstream-consumer integration suites pass against the immutable Hubuum 0.0.3 image.