Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5

Legacy azure_core writes the authorization header value to logs

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (azure_core 0.22.0, 0.2.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io azure_core

    Affected
    >= 0.0.0-0, < 0.2.0>= 0.2.1-0, < 0.22.0
    Fixed in
    0.2.0, 0.22.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Applications built on the legacy Azure SDK for Rust (`azure_core` 0.21.0 and earlier) write the value of the outgoing `authorization` header to their logs whenever debug-level logging is enabled, and in every affected version also at trace level. The leaked values are live credentials — Microsoft Entra ID bearer tokens, Azure Storage SharedKey signatures, and SAS tokens — and anyone with read access to the logs can replay them until they expire (CWE-532). Versions 0.22.0 and later, which are the rewritten and currently supported SDK, do not contain the affected code.

Affected versions Every published legacy version except 0.2.0 writes the `authorization` header value to logs: 0.1.1 (2022-01-25), and 0.2.1 through 0.21.0 (2024-10-15).

Mitigation - Upgrade to `azure_core` 1.0.0 or newer. - If you are unable to upgrade, raise the log level above debug for the impacted crates or submit a feature request for missing crates built on `azure_core` 1.0.0 or newer. - Treat logs produced…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record RUSTSEC-2026-0275

Agent brief

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

# Patch Next advisory brief: rustsec-2026-0275

Advisory: Legacy `azure_core` writes the `authorization` header value to logs
IDs: rustsec-2026-0275
Record: https://patchnext.com/advisories/rustsec-2026-0275 (revision 1, source checked 23 Oct 2026, 22:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: azure_core 0.22.0, 0.2.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io azure_core: affected >= 0.0.0-0, < 0.2.0; >= 0.2.1-0, < 0.22.0; fixed in 0.2.0, 0.22.0

## Suggested inspection (read-only)
- crates.io azure_core: 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 azure_core.
- 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://osv.dev/vulnerability/RUSTSEC-2026-0275 (OSV record RUSTSEC-2026-0275 lists affected ranges: crates.io azure_core >=0.0.0-0 =0.2.1-0 <0.22.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…