msal 1.39.0
- Source
- https://github.com/AzureAD/microsoft-authentication-library-for-python
- Tag scanned
1.39.0- Compared with
1.38.0(0 signals introduced since)- Files
- 84 scanned, 14 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 16 info
- Scan time
- 8.2 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 10 of 10 warn and critical signals; 10 demoted to info.
- Disclude version
- 4.1.0
- Scanned (UTC)
- 2026-10-22 05:45
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
[](https://github.com/AzureAD/microsoft-authentication-library-for-python/actions) | [ for RSA, written as a string constant in the MSAL library's own CLI module. The base64url fields are public key material and the pattern is ordinary for JWK handling. Nothing decodes or executes the blob.
-
--4--dismissed The tail of the same hardcoded RSA JWK constant, ending in the public exponent.Reasoning
This is the continuation of the same JWK constant (the n value's tail and the e=AQAB exponent). It is a normal base64url key encoding with no execution or decoding path.
-
= # KAP 1P Server App Scope, obtained from https://github.com/Azure/azure-cli-extensions/pull/4468/files#diff-a47efa3186c7eb4f1176e07d0b858ead0bf4a58bfd51e448ee3607a5b4ef47f6R116 = -
# Its API description is available in site-packages/pymsalruntime/PyMsalRuntime.pyi -
# MSAL's HttpResponse did not have headers until 1.23.0 # https://github.com/AzureAD/microsoft-authentication-library-for-python/pull/581/files#diff-28866b706bc3830cd20485685f20fe79d45b58dce7050e68032e9d9372d68654R61 # This helper ensures graceful degradation to {} without exception -
= -
=dismissed A test fixture RSA JWK string in a broker test script.Reasoning
This is the same RSA JWK test fixture as in the library module, here in a broker test script. Test fixtures commonly carry key material like this, and nothing is decoded or executed.
-
--4--dismissed The tail of the RSA JWK test fixture in the broker test script.Reasoning
This is the tail of the same JWK test fixture, a standard base64url key encoding in a test file.
-
: # MSAL asks for client_info, so it would be available , })dismissed A base64url-encoded client_info claim blob used as test input.Reasoning
The value is a base64url-encoded JSON object (uid/utid claims) passed as client_info in a unit test. This is the standard MSAL client_info format, and the test asserts on it. It is not a payload.
-
=dismissed The RSA JWK test fixture reused in the end-to-end test file.Reasoning
The end-to-end test repeats the same RSA JWK fixture seen in the library and broker test files. This is test data for key handling.
-
--4--dismissed The tail of the RSA JWK test fixture in the end-to-end test file.Reasoning
This is the tail of the same JWK test fixture in the end-to-end test, a standard base64url key encoding.
-
, # Azure CLI's connectedk8s plugin uses this # https://github.com/Azure/azure-cli-extensions/pull/4468/files#diff-a47efa3186c7eb4f1176e07d0b858ead0bf4a58bfd51e448ee3607a5b4ef47f6R116 ] -
= =dismissed A test JWT constant representing an expired ID token.Reasoning
This is a JWT with a header and claims (iss/iat/exp/aud/sub) and a signature, used as an EXPIRED_ID_TOKEN constant in an OIDC unit test. Its claims are plausible test values and show no sign of malicious use.
-
=likely benign A PEM private key test fixture embedded in a test file.Reasoning
This is a PEM-armored private key constant in a test for optional thumbprint handling. The key text looks like a generated test value, and the file's purpose is consistent with fixture use. Hardcoded test keys are a known false positive for base64 detection.
-
=likely benign A PEM certificate test fixture in the same test file.Reasoning
This is a PEM certificate test fixture (BEGIN CERTIFICATE with an example CA subject) in the same test file. It is standard test data and not an obfuscated payload.
Reproduce This Scan
Run disclude locally to verify. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.
&&