CVE-2026-50202
MediumCVSS 5.9Exploitation Probability (EPSS)
Low risk20th percentile - higher than 20% of all known CVEs
Summary
In Steeltoe projects prior to versions 3.4.0 (CloudFoundryBase), 4.2.0 (JwtBearer), and 4.2.0 (OpenIdConnect), there is an issue with the JWT signing key cache. The `kid` is used as the sole cache key, which can lead to unauthorized token validation in applications with multiple `JwtBearer` schemes pointing to different identity providers.
Risk Assessment
The organization may be exposed to attacks where signing keys from one identity provider are used to validate tokens from another, potentially leading to unauthorized access. Additionally, the lack of expiration for cached keys increases the risk associated with key rotation or revocation.
Recommendation
Immediate upgrade to versions 3.4.0 (CloudFoundryBase), 4.2.0 (JwtBearer), and 4.2.0 (OpenIdConnect) is recommended. If an upgrade is not possible, configure only one `JwtBearer` scheme per application when different identity providers are required and restart the application process after an identity provider signing key rotation.
Related vulnerabilities
- CVE-2026-109157Critical
The TRENDnet TEW-432BRP router version 3.10B20 contains a stack-based buffer overflow in the formTcpipSetup function of /goform/formTcpipSetup. Manipulating the Name argument allows remote attack, and the exploit has been publicly disclosed.
- CVE-2026-63354Critical
Affected devices do not properly validate and sanitize visual marker data contained in imported CSV trace files before rendering it on the Trace page. An attacker can socially engineer an authorized user with the 'Read diagnostics' right into importing a crafted trace file.
- CVE-2026-63353Critical
Affected devices do not properly sanitize comment fields contained in imported trace files before rendering them on the Trace page. An attacker can socially engineer an authorized user with the 'Read diagnostics' right into importing a crafted trace file.
- CVE-2026-63350Critical
Affected devices do not properly restrict executable content contained in imported trace files. An attacker can socially engineer an authorized user with the 'Read diagnostics' right into importing a crafted trace file.
- CVE-2026-44415Critical
Affected systems do not properly restrict access to internal APIs and paths for authenticated users. An authenticated remote attacker could access sensitive internal information.
- CVE-2026-109110Critical
The Wavlink WL-WN592AX6 router version 250422 contains a vulnerability in the system function of the wmapd daemon component. Manipulation of an argument leads to OS command injection, and the attack can be launched remotely.
- CVE-2026-109109Critical
The Wavlink WL-WN530BE1-A router version 251117 contains a stack-based buffer overflow in the strcpy function of /cgi-bin/ExportAllSettings.cgi in the Settings Export CGI component. Manipulating the HTTP_COOKIE/X-Cmd argument allows remote attack.
- CVE-2026-109108Critical
The Wavlink WL-WN530BE1-A router version 251117 contains a vulnerability in the popen function of /cgi-bin/uploadVpn.cgi. Manipulating the Type argument leads to OS command injection, and the attack can be performed remotely.
- CVE-2026-108971Critical
A flaw has been found in D-Link DCS-930L B1.08B4 affecting the mpfd_decode function in bootloader_region.bin of the Emergency HTTP Recovery Server component. Manipulating the firmware argument leads to improper verification of the cryptographic signature. The attack can be performed remotely and the exploit has been published.
- CVE-2026-109758Critical
Perforce Helix Authentication Service (HAS) versions 2022.1-2025.2 retain a default SCIM bearer token that is not automatically replaced with a random value during installation. An attacker knowing this token can gain unauthorized access to the SCIM API and perform user and group operations. This issue can be chained with CVE-2026-61834, potentially leading to remote code execution.
Original NVD description (English source)
Steeltoe is an open source project that provides a collection of libraries that helps users build cloud-native applications. In Steeltoe.Security.Authentication.CloudFoundryBase prior to version 3.4.0, Steeltoe.Security.Authentication.JwtBearer prior to version 4.2.0, and Steeltoe.Security.Authentication.OpenIdConnect prior to version 4.2.0, the JWT signing key cache in `TokenKeyResolver` uses `kid` as the sole cache key without namespacing by authority. In applications with multiple `JwtBearer` schemes pointing to different identity providers, a key fetched for one scheme can satisfy token validation for another. Additionally, cached keys have no expiration, so rotated or revoked keys remain trusted until the application process restarts. Steeltoe.Security.Authentication.CloudFoundryBase version 3.4.0, Steeltoe.Security.Authentication.JwtBearer version 4.2.0, and Steeltoe.Security.Authentication.OpenIdConnect version 4.2.0 patch the issue. If an immediate upgrade is not possible: In multi-scheme deployments, configure only one `JwtBearer` scheme per application when different identity providers are required; and/or restart the application process after an identity provider signing key rotation to clear stale cached keys.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS