CVE-2026-110985

waiting for further signals

EUVD-2026-112207 ↗

no check availablenot proven exploitable

cve.orgpublic pockev

Apache Software Foundation Apache Kafka >= 4.1.0, <= 4.1.2; >= 4.2.0, <= 4.2.1; 4.3.0

CWE-345 Insufficient Verification of Data Authenticity, CWE-347 Improper Verification of Cryptographic Signature, CWE-636 Not Failing Securely ('Failing Open'), CWE-1287 Improper Validation of Specified Type of Input

ETK-2026-2887, permanent identifier

2h 36msince last run

1h 44mAI analysis

timeline

0 = trigger signal

trigger signal (cve.org) +0hwaiting for further signals+2h28m

+4h

+6h

+8h

+10h

+12h

description

Apache Kafka brokers can accept forged OAuth bearer tokens when SASL/OAUTHBEARER uses the default validator without a JWKS endpoint or a custom signature-verifying key resolver. An unauthenticated network attacker able to reach the affected listener may impersonate arbitrary principals, including privileged accounts.

mitigation

Configure a JWKS endpoint for every affected OAuth bearer listener, or use a validator backed by a signature-verifying key resolver. Upgrade to Kafka 4.2.2, 4.3.1, or 4.4.0 to prevent brokers from starting with this unsafe fallback.

check

exploit

automation

–

auth required

–

EPSS

–

agent run time

1h 44m

cve.org record, t = 0

2026-10-28 16:37Z

Δ to public poc

–

Δ to kev

–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

2026-10-28 16:37Z
cve_org: trigger signal, started the run
https://www.cve.org/CVERecord?id=CVE-2026-110985

this entry in the feed

GET /api/v1/feed/CVE-2026-110985

{
  "etk_id": "ETK-2026-2887",
  "cve_id": "CVE-2026-110985",
  "display_id": "CVE-2026-110985",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-112207",
  "status": "published",
  "anchor_state": "anchored",
  "title": "JWT signature validation bypass in Apache Kafka brokers",
  "summary": "Apache Kafka brokers can accept forged OAuth bearer tokens when SASL/OAUTHBEARER uses the default validator without a JWKS endpoint or a custom signature-verifying key resolver. An unauthenticated network attacker able to reach the affected listener may impersonate arbitrary principals, including privileged accounts.",
  "mitigation": "Configure a JWKS endpoint for every affected OAuth bearer listener, or use a validator backed by a signature-verifying key resolver. Upgrade to Kafka 4.2.2, 4.3.1, or 4.4.0 to prevent brokers from starting with this unsafe fallback.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Kafka",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.1.0, <= 4.1.2",
        ">= 4.2.0, <= 4.2.1",
        "4.3.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "org.apache.kafka:kafka",
      "purl": null
    }
  ],
  "cwes": [
    345,
    347,
    636,
    1287
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 103.78257685,
  "t0_at": "2026-10-28T16:37:45.688000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-28T16:37:45.688000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T16:37:45.688000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110985"
    }
  }
}

published 2026-10-28 17:22Z
last change 2026-10-28 21:25Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.