CVE-2026-11922: CWE-290 Authentication Bypass by Spoofing in zenml-io zenml-io/zenml
A vulnerability in zenml-io/zenml versions 0.57.0 through 0.94.2 allows attackers to bypass rate-limiting on login and password-change endpoints by manipulating the X-Forwarded-For header. This occurs because the rate limiter uses the client IP derived from this header, which can be spoofed when Uvicorn is configured with certain proxy header options. This bypass enables unthrottled credential guessing attacks. The vulnerability has a medium severity with a CVSS score of 6.5. No official patch or remediation guidance is currently provided by the vendor.
AI Analysis
Technical Summary
CVE-2026-11922 is an authentication bypass vulnerability in zenml-io/zenml (versions 0.57.0 to 0.94.2) that allows attackers to circumvent rate-limiting protections on the POST /api/v1/login and self password-change endpoints. The issue arises because the rate limiter keys requests based on request.client.host, which is derived from the X-Forwarded-For header when Uvicorn is launched with the --proxy-headers and --forwarded-allow-ips * options. Since clients can control the X-Forwarded-For header, they can rotate the client IP value and bypass rate limits, enabling unthrottled credential guessing attacks. No known exploits in the wild have been reported, and no official fix or patch is documented.
Potential Impact
The vulnerability allows attackers to bypass rate-limiting on authentication-related endpoints by spoofing the client IP address via the X-Forwarded-For header. This can lead to unthrottled credential guessing attacks, increasing the risk of unauthorized access through brute force or password guessing. The confidentiality and integrity of user accounts are at risk, but availability is not impacted.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider disabling or restricting the use of the --proxy-headers and --forwarded-allow-ips * options in Uvicorn to prevent clients from controlling the client IP used for rate limiting. Additionally, implementing alternative rate-limiting strategies that do not rely solely on the X-Forwarded-For header or client IP may help mitigate this issue.
CVE-2026-11922: CWE-290 Authentication Bypass by Spoofing in zenml-io zenml-io/zenml
Description
A vulnerability in zenml-io/zenml versions 0.57.0 through 0.94.2 allows attackers to bypass rate-limiting on login and password-change endpoints by manipulating the X-Forwarded-For header. This occurs because the rate limiter uses the client IP derived from this header, which can be spoofed when Uvicorn is configured with certain proxy header options. This bypass enables unthrottled credential guessing attacks. The vulnerability has a medium severity with a CVSS score of 6.5. No official patch or remediation guidance is currently provided by the vendor.
CVSS v3.0
Score 6.5medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-11922 is an authentication bypass vulnerability in zenml-io/zenml (versions 0.57.0 to 0.94.2) that allows attackers to circumvent rate-limiting protections on the POST /api/v1/login and self password-change endpoints. The issue arises because the rate limiter keys requests based on request.client.host, which is derived from the X-Forwarded-For header when Uvicorn is launched with the --proxy-headers and --forwarded-allow-ips * options. Since clients can control the X-Forwarded-For header, they can rotate the client IP value and bypass rate limits, enabling unthrottled credential guessing attacks. No known exploits in the wild have been reported, and no official fix or patch is documented.
Potential Impact
The vulnerability allows attackers to bypass rate-limiting on authentication-related endpoints by spoofing the client IP address via the X-Forwarded-For header. This can lead to unthrottled credential guessing attacks, increasing the risk of unauthorized access through brute force or password guessing. The confidentiality and integrity of user accounts are at risk, but availability is not impacted.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider disabling or restricting the use of the --proxy-headers and --forwarded-allow-ips * options in Uvicorn to prevent clients from controlling the client IP used for rate limiting. Additionally, implementing alternative rate-limiting strategies that do not rely solely on the X-Forwarded-For header or client IP may help mitigate this issue.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- @huntr_ai
- Date Reserved
- 2026-06-10T17:41:21.911Z
- Cvss Version
- 3.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a62de069c2644c7f835c47d
Added to database: 07/24/2026, 03:37:42 UTC
Last enriched: 07/24/2026, 03:52:37 UTC
Last updated: 07/24/2026, 04:50:27 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.