CVE-2026-110985
Tenable Plugin
Checking the public Tenable catalog…
AI Threat Summary
CVE-2026-110985 is a moderate vulnerability affecting the target software. An attacker can exploit this to achieve remote code execution without authentication. Threat hunters should monitor for exploit attempts and apply vendor patches immediately.
Description
A Kafka broker using SASL/OAUTHBEARER with the default validator (sasl.oauthbearer.jwt.validator.class=DefaultJwtValidator) selects its implementation from configuration. When sasl.oauthbearer.jwks.endpoint.url is set, the validator verifies the JWT signature. When that URL is unset (the default) and no verification key resolver is supplied, DefaultJwtValidator silently falls back to ClientJwtValidator, which does not verify the JWT signature, algorithm, or issuer - and the broker starts with no warning or error. This is the residual of CVE-2026-33557, whose fix restored signature verification only on the path where the JWKS endpoint URL is set. Impact: A broker in this state accepts any structurally valid JWT, including "alg":"none" tokens. An unauthenticated remote attacker who can reach the listener can forge a token asserting any principal - including configured superusers - and gain full access to the cluster. Only brokers that enable SASL/OAUTHBEARER validation without a JWKS endpoint URL (and without a custom verification key resolver) are affected; brokers that set the URL verify signatures and are not affected. Unlike CVE-2026-110952 (issuer/audience not enforced by default), here no signature is verified at all. Mitigation (all affected versions, no upgrade required): Set sasl.oauthbearer.jwks.endpoint.url for every listener/mechanism that uses OAuthBearerValidatorCallbackHandler, or configure a signature-verifying sasl.oauthbearer.jwt.validator.class. Resolution: From Apache Kafka 4.2.2, 4.3.1, and 4.4.0: a broker that would fall back to the non-verifying ClientJwtValidator fails to start with a ConfigException instead of running without signature verification (secure by default).
Attack Chain
Attacker identifies vulnerable service instances using Shodan, Censys, or active scanning
Attacker crafts malicious payload exploiting CVE-2026-110985 to achieve remote code execution
Attacker executes arbitrary OS commands or shellcode in the context of the vulnerable process
Attacker installs backdoor, cron job, or web shell for persistent access
Attacker uses compromised host as pivot point to access internal network resources
MITRE ATT&CK Techniques
Attacker exploits the vulnerability in an internet-facing service to gain initial access
Post-exploitation shell commands executed through the vulnerability
Attacker downloads malware or tools after gaining code execution
Indicators of Compromise
| Type | Value | Description | |
|---|---|---|---|
| user_agent | Mozilla/5.0 (compatible; exploit/1.0) |
Generic exploit scanner user agent pattern | |
| url | /api/vuln-endpoint?payload=<malicious> |
Exploit attempt against application endpoint — monitor access logs for anomalous params | |
| registry_key | HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\backdoor |
Persistence mechanism after successful RCE |
Remediation
Quick Facts
| CVE ID | CVE-2026-110985 |
| CVSS Score | N/A |
| Published | 2026-10-28 |
| Exploited | No |
| CISA KEV | No |
| PoC | Not public |