Hubuum client library (Rust): Sensitive data may be exposed through default diagnostics

Exploitation

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

CVSS 4.0

2.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/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.

Summary hubuumclient diagnostics can expose sensitive request, response, import/export, task, delivery, or server-provided data when applications format or log errors and public models. Affected behavior Native reqwest::Error values retain the full request URL. Converting those errors into ApiError::Http, or exhausting retries and storing the error text in ApiError::RetryExhausted, preserves query parameter values. Detailed HTTP and decoding errors can retain server-provided messages, response bodies, or payload details, including through error source chains. Several public response and model types also derived or implemented diagnostics over untrusted or secret-adjacent fields. These include raw response bodies and cursors; rendered and JSON export payloads; import schemas and object data; task summaries, links, output URLs, events, and import-result details; event-delivery claims and errors; event sink configuration; subscription routing; and remote-call failure details. High-level…

Published by the source

24 Jul 2026, 21:49 UTC

Last modified by the source

24 Jul 2026, 21:49 UTC

Source last checked

26 Oct 2026, 15:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2625-rw7m-5q5x

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

# Patch Next advisory brief: GHSA-2625-rw7m-5q5x

Advisory: Hubuum client library (Rust): Sensitive data may be exposed through default diagnostics
IDs: GHSA-2625-rw7m-5q5x
Record: https://patchnext.com/advisories/ghsa-2625-rw7m-5q5x (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: Low (CVSS 2.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.6.0; 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-2625-rw7m-5q5x (GitHub-reviewed advisory GHSA-2625-rw7m-5q5x lists affected ranges: crates.io hubuum_client >=0 <=0.6.0)

Commands are suggestions: review each one before running it.