CVE-2025-32016

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?
You can work around the issue in the following ways:

• Ensure that service logs are handled securely and access to logs is restricted

• Don’t use LogLevel = Information for the Microsoft.Identity.Web namespace

Recommendation for production environment

Avoid using ClientCredentials with CredentialDescriptions which CredentialSource is ClientSecret, or Base64Encoded, or Path. Rather use certificate from KeyVault or a certificate store, or Federation identity credential with Managed identity.

References

Are there any links users can visit to find out more?

What kind of vulnerability is it? Who is impacted?

Description: This vulnerability affects confidential client applications, including daemons, web apps, and web APIs. Under specific circumstances, sensitive information such as client secrets or certificate details may be exposed in the service logs of these applications. Service logs are intended to be handled securely.

Impact: The vulnerability impacts service logs that meet the following criteria:

• Logging Level: Logs are generated at the information level.
• Credential Descriptions: containing:
  • Local file paths with passwords.
  • Base64 encoded values.
  • Client secret.

Additionally, logs of services using Base64 encoded certificates or certificate paths with password credential descriptions are also affected if the certificates are invalid or expired, regardless of the log level. Note that these credentials are not usable due to their invalid or expired status.

If your service logs are handled securely, you are not impacted.

Otherwise, the following table shows when you can be impacted

  | Log Level Information for Microsoft.Identity.Web | Invalid Certificate
-- | -- | --
One of the ClientCredentials credential description has a CredentialSource = Base64Encoded or (CredentialSource = Path) | Impacted | Impacted
One of the ClientCredentials credential description is a Client secret (CredentialSource = ClientSecret) | Impacted | Not impacted
Other credential descriptions | Not Impacted | Not Impacted

CVE-2025-32016 has a CVSS score of 4.7 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.8.2, 9.0.0); upgrading removes the vulnerable code path.

Kodem intelligence

Has the problem been patched? What versions should users upgrade to?
To mitigate this vulnerability, update to Microsoft.Identity.Web 3.8.2 or Microsoft.Identity.Abstractions 9.0.0.

1. What is CVE-2025-32016? CVE-2025-32016 is a medium-severity security vulnerability in Microsoft.Identity.Web (nuget), affecting versions >= 3.2.0, < 3.8.2. It is fixed in 3.8.2, 9.0.0.
2. How severe is CVE-2025-32016? CVE-2025-32016 has a CVSS score of 4.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-32016?
   • Microsoft.Identity.Web (nuget) (versions >= 3.2.0, < 3.8.2)
   • Microsoft.Identity.Abstractions (nuget) (versions >= 7.1.0, < 9.0.0)
4. Is there a fix for CVE-2025-32016? Yes. CVE-2025-32016 is fixed in 3.8.2, 9.0.0. Upgrade to this version or later.
5. Is CVE-2025-32016 exploitable, and should I be worried? Whether CVE-2025-32016 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-32016 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-32016?
   • Upgrade Microsoft.Identity.Web to 3.8.2 or later
   • Upgrade Microsoft.Identity.Abstractions to 9.0.0 or later