Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Check if your repositories are affected!View on GitHub
Search

RUSTSEC-2026-0275

MediumCVSS 6.5 / 10
Published Aug 15, 2026·Last modified Sep 1, 2026
Affected Components(2)
crates.io logoazure_core
0.2.1-0 – 0.22.0
crates.io logoazure_core
0.0.0-0 – 0.2.0
Description

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 by an affected build as credential-bearing: rotate any long-lived secret that authenticated a request while debug logging was on.

Coordination

The finding was reported to the Microsoft Security Response Center (VULN-211331), which determined that it does not meet the Microsoft Security Servicing Criteria definition of a security vulnerability.

It was then disclosed publicly as Azure/azure-sdk-for-rust#5074 on 2026-08-15, asking the maintainers to confirm the behavior so that an advisory could be filed for the legacy crates. A maintainer replied on 2026-08-26 and closed the issue as not planned: the legacy branch is unsupported, there are no plans to update it, and users should move to crates built on azure_core 1.0.0 or newer.

Upload your SBOM

Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.

Risk Scores
Base Score
6.5

The vulnerability requires local access to the device to be exploited. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The vulnerability can affect other systems as well, not just the initial system. There is a high impact on the confidentiality of the information.

Threat Intelligence
6.0

Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.

EPSS
N/A

Probability that this vulnerability will be exploited in the wild within the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Medium severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard