{"answers":{"affected":"2 open source packages ship an affected version, including hubuum_client.","exploited":"There is no known exploitation of GHSA-f45q-w629-wr25 in the wild and no public exploit code.","fix":"Upgrade hubuum_client to 0.6.1 or later.","what":"GHSA-f45q-w629-wr25 is a vulnerability in hubuum_client, published on 24 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-f45q-w629-wr25 and fix it if it is affected.\n\nWhat it is: GHSA-f45q-w629-wr25 is a vulnerability in hubuum_client, published on 24 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-f45q-w629-wr25 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- hubuum_client (crates.io): affected from 0.0.1; fixed in 0.6.1\n- hubuum_client (crates.io): affected from 0.0.1; fixed in 0.6.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-f45q-w629-wr25/ (Markdown: https://insights.sbomify.com/GHSA-f45q-w629-wr25/index.md)","id":"GHSA-f45q-w629-wr25","markdown":"https://insights.sbomify.com/GHSA-f45q-w629-wr25/index.md","name":"GHSA-f45q-w629-wr25","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust client library","requires_auth":"low_privilege","summary":"Authenticated requests may leak bearer tokens to other paths on the same origin via redirects, exposing sensitive credentials to attackers or compromised servers.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"## Impact\n\nThe 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.\n\nExploitation 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.\n\n## Patches\n\nVersion 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.\n\n## Workarounds\n\nOn 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.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Hubuum client library (Rust): Authenticated requests may escape the configured base path through redirects","id":"GHSA-f45q-w629-wr25","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0.0.1"],"last_affected":[],"package":"hubuum_client","purl":null,"source":"GHSA-f45q-w629-wr25"},{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0.0.1"],"last_affected":[],"package":"hubuum_client","purl":"pkg:cargo/hubuum_client","source":"GHSA-f45q-w629-wr25"}],"products":null,"published":"2026-07-24","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Authenticated requests may leak bearer tokens to other paths on the same origin via redirects, exposing sensitive credentials to attackers or compromised servers.","url":"https://insights.sbomify.com/GHSA-f45q-w629-wr25/"}