Hubuum client library (Rust): Sensitive data may be exposed through default diagnostics
The Hubuum client library for Rust versions prior to 0.6.1 can expose sensitive data through its default diagnostics. This occurs because error handling and diagnostic outputs may include full request URLs with query parameters, server response bodies, and other secret-adjacent details. Applications that log these diagnostics risk writing sensitive information such as credentials, tokens, and internal data to logs. The issue is addressed by redacting sensitive query values and sanitizing diagnostic outputs to exclude secret or sensitive content.
AI Analysis
Technical Summary
The vulnerability in hubuum_client (Rust) involves the exposure of sensitive data through default diagnostic outputs. Native reqwest::Error values retain full request URLs including query parameters, which are preserved when converted into ApiError variants. Diagnostic implementations on various public response and model types include untrusted or secret-adjacent fields such as raw response bodies, import/export data, task summaries, event details, and configuration. As applications often log these diagnostics, sensitive information can be inadvertently exposed. The remediation involves redacting query parameters from URLs in errors, sanitizing diagnostic outputs to exclude sensitive data, and modifying error handling to avoid including detailed server messages or payloads in default diagnostics.
Potential Impact
Sensitive information including credentials, tokens, query parameters, server response bodies, and other secret-adjacent data may be exposed in application logs or error outputs. This exposure could lead to information disclosure risks if logs are accessed by unauthorized parties. The severity is considered low based on the available data and CVSS 4.0 vector indicating network attack vector, low complexity, and limited privileges required.
Mitigation Recommendations
A fix is available that redacts query parameter values from embedded request URLs before storing HTTP errors and applies similar sanitization to retry exhaustion errors. Default error and model diagnostics have been updated to report only safe metadata, excluding server messages, payloads, cursors, links, configuration, or secret-adjacent details. Applications that require access to original values can still explicitly use response, error, task, import, export, event, and delivery APIs. Users should upgrade to version 0.6.1 or later to benefit from these fixes.
Hubuum client library (Rust): Sensitive data may be exposed through default diagnostics
Description
The Hubuum client library for Rust versions prior to 0.6.1 can expose sensitive data through its default diagnostics. This occurs because error handling and diagnostic outputs may include full request URLs with query parameters, server response bodies, and other secret-adjacent details. Applications that log these diagnostics risk writing sensitive information such as credentials, tokens, and internal data to logs. The issue is addressed by redacting sensitive query values and sanitizing diagnostic outputs to exclude secret or sensitive content.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in hubuum_client (Rust) involves the exposure of sensitive data through default diagnostic outputs. Native reqwest::Error values retain full request URLs including query parameters, which are preserved when converted into ApiError variants. Diagnostic implementations on various public response and model types include untrusted or secret-adjacent fields such as raw response bodies, import/export data, task summaries, event details, and configuration. As applications often log these diagnostics, sensitive information can be inadvertently exposed. The remediation involves redacting query parameters from URLs in errors, sanitizing diagnostic outputs to exclude sensitive data, and modifying error handling to avoid including detailed server messages or payloads in default diagnostics.
Potential Impact
Sensitive information including credentials, tokens, query parameters, server response bodies, and other secret-adjacent data may be exposed in application logs or error outputs. This exposure could lead to information disclosure risks if logs are accessed by unauthorized parties. The severity is considered low based on the available data and CVSS 4.0 vector indicating network attack vector, low complexity, and limited privileges required.
Mitigation Recommendations
A fix is available that redacts query parameter values from embedded request URLs before storing HTTP errors and applies similar sanitization to retry exhaustion errors. Default error and model diagnostics have been updated to report only safe metadata, excluding server messages, payloads, cursors, links, configuration, or secret-adjacent details. Applications that require access to original values can still explicitly use response, error, task, import, export, event, and delivery APIs. Users should upgrade to version 0.6.1 or later to benefit from these fixes.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2625-rw7m-5q5x
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["crates.io"]
- Database Specific Severity
- LOW
- Cvss Version
- 4.0
Threat ID: 6a6542219c2644c7f80884bd
Added to database: 07/25/2026, 23:09:21 UTC
Last enriched: 07/25/2026, 23:52:00 UTC
Last updated: 07/26/2026, 01:10:34 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.