Hubuum client library (Rust): Authenticated requests may escape the configured base path through redirects

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact The built-in async and blocking clients used reqwest's default redirect policy. BaseUrl constrains the initial request to the configured origin and path prefix, but redirect processing occurs after that validation. reqwest retains sensitive headers when a redirect changes only the path on the same scheme, host, and port. A redirect from a Hubuum endpoint to another path on a shared origin could therefore carry the bearer Authorization header outside the configured Hubuum path prefix. Exploitation requires an attacker, compromised server, or intermediary to influence a 3xx response. Cross-origin redirects are not affected because reqwest strips sensitive headers when scheme, host, or port changes. Patches Version 0.6.1 configures both built-in HTTP clients with reqwest::redirect::Policy::none(). Redirect responses are returned as 3xx API errors instead of being followed. Supplying a preconfigured reqwest client remains an explicit opt-in to that client's redirect policy.…

Published by the source

24 Jul 2026, 21:48 UTC

Last modified by the source

24 Jul 2026, 21:48 UTC

Source last checked

26 Oct 2026, 15:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f45q-w629-wr25

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-f45q-w629-wr25

Advisory: Hubuum client library (Rust): Authenticated requests may escape the configured base path through redirects
IDs: GHSA-f45q-w629-wr25
Record: https://patchnext.com/advisories/ghsa-f45q-w629-wr25 (revision 1, source checked 26 Oct 2026, 15:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: hubuum_client 0.6.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io hubuum_client: affected >= 0.0.1, < 0.6.1; fixed in 0.6.1

## Suggested inspection (read-only)
- crates.io hubuum_client: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on hubuum_client.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f45q-w629-wr25 (GitHub-reviewed advisory GHSA-f45q-w629-wr25 lists affected ranges: crates.io hubuum_client >=0.0.1 <0.6.1)

Commands are suggestions: review each one before running it.