Improper URL Validation Enables API Key Theft

NextChat versions from 2.15.8 through 2.16.1 contain an improper URL validation vulnerability in the proxy endpoint that allows attackers to obtain the server's OpenAI API key. The x-base-url header is validated using substring matching instead of hostname parsing, allowing any URL containing 'api.openai.com' to pass validation and receive the server's credentials in the Authorization header.

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

NextChat versions 2.15.8 through 2.16.1 suffer from a critical input validation flaw (CWE-20) in their proxy endpoint that exposes OpenAI API keys to unauthorized attackers. The vulnerability stems from using substring matching to validate the x-base-url header rather than implementing proper hostname parsing. This allows attackers to bypass security controls by crafting URLs that contain the string 'api.openai.com' anywhere in the path, tricking the server into forwarding sensitive Authorization headers containing valid API credentials. With a CVSS score of 7.5, this high-severity issue affects any organization running vulnerable NextChat instances that rely on OpenAI integrations, potentially compromising API quotas, enabling unauthorized API usage, and exposing proprietary AI model interactions.

Casky's 323 matched security skills leverage Claude's extended reasoning to detect the attack patterns underlying this vulnerability across MITRE ATT&CK techniques TA0001 (Reconnaissance) and TA0043 (Resource Development). Practitioners using Casky would identify reconnaissance attempts through monitoring for suspicious x-base-url header patterns that contain 'api.openai.com' substrings combined with non-standard domains, as well as resource development activities involving credential harvesting and API key exfiltration. The platform's skill mapping would surface detection rules for malformed proxy requests, Authorization header leakage in HTTP responses, and anomalous API key usage patterns. Security teams would see findings highlighting the exact validation bypass technique—substring injection in headers—alongside recommended mitigations including hostname canonicalization, allowlist-based URL validation, and runtime monitoring for API key exposure in proxy logs.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-82639.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-82639

Casky has 323 skills that investigate the attack patterns behind CVE-2026-82639. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn