Loading vulnerability…
CVE-2026-50338 is an improper authentication vulnerability in Azure Spring Apps. The flaw allows an authorized attacker to elevate privileges over a network because authentication is not correctly enforced for certain operations or access paths. Based on the available information, exploitation does not require unauthenticated access, but instead relies on an attacker already possessing valid access to the affected service and then abusing the authentication weakness to obtain higher privileges than intended.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Small repository containing a single Python proof-of-concept exploit (poc.py), a README with vulnerability details and usage, and a GPL license. The PoC targets CVE-2026-50338, a cross-issuer authentication bypass in Spring Cloud Azure B2C resource server auto-configuration affecting spring-cloud-azure-starter-active-directory-b2c <= 5.19.0. The exploit workflow is: (1) send an unauthenticated baseline request to the supplied target endpoint and expect 401, (2) obtain an OAuth2 client_credentials access token from Microsoft Entra ID using either MSAL or a raw POST to the Microsoft token endpoint, (3) decode JWT claims locally to confirm the issuer is an AAD-line issuer rather than B2C, and (4) replay the token to the B2C-protected API in an Authorization: Bearer header. A 200 response is treated as successful exploitation, while 401 indicates the target is patched. The code is operational rather than a mere detector because it actively acquires and uses a token to authenticate to the target, but it does not deliver code execution or a shell; its capability is unauthorized API access via authentication bypass. The repository structure is straightforward: README.md explains the vulnerability mechanics, prerequisites, and command-line usage; poc.py implements argument parsing, token acquisition, JWT claim inspection, and target request logic.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.