How severe is GHSA-f45q-w629-wr25?

No CVSS score has been assigned to GHSA-f45q-w629-wr25 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f45q-w629-wr25?

GHSA-f45q-w629-wr25 affects the following packages: hubuum_client (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-f45q-w629-wr25?

Update hubuum_client to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f45q-w629-wr25 is resolved across your whole dependency graph.

How do I detect GHSA-f45q-w629-wr25 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hubuum_client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-f45q-w629-wr25 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-f45q-w629-wr25 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f45q-w629-wr25 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-f45q-w629-wr25 published, and has it been updated?

GHSA-f45q-w629-wr25 was published on July 24, 2026 and was last updated on July 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

Hubuum client library (Rust): Authenticated requests may escape the configured base path through redirectsGHSA-f45q-w629-wr25

Fix: hubuum/hubuum-client-rust@5a5c275

GHSA-f45q-w629-wr25 is a security vulnerability in hubuum_client. A fix is available for hubuum_client — see the affected versions and patch details below.

Published

Jul 24, 2026

Updated

Jul 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 24, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀hubuum_client

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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.

Workarounds

On affected versions, construct a reqwest client with reqwest::redirect::Policy::none() and pass it through with_http_client. Deployments can also reduce exposure by ensuring the Hubuum origin is not shared with other applications and that trusted infrastructure never redirects API requests outside the configured path prefix.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`hubuum_client`	≥ 0.0.1&&< 0.6.1	0.6.1`cargo update -p hubuum_client --precise 0.6.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hubuum_client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update hubuum_client to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f45q-w629-wr25 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-f45q-w629-wr25 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works