CVE-2026-133325

waiting for further signalsZero needs more public information before it can validate it.

GHSA-j322-r8cv-7j54 ↗EUVD-2026-130776 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Apache Software Foundation Apache Tomcat >= 11.0.28, <= 11.0.29; 10.1.62; 9.0.124
CWE-322 Key Exchange without Entity Authentication
ETK-2026-4975Zero's internal tracking ID, independent of the CVE number., permanent identifier
7h 27msince last run
21mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h44m
0
+2h
+6h
+8h
+10h
+12h

description

Apache Tomcat 11.0.29, 10.1.62, and 9.0.124 cluster deployments may not authenticate joining peers when using TLS 1.3 with TLS-PSK. An unauthenticated system could join the cluster if that configuration is enabled.

mitigation

Reconfigure cluster connections to use TLS 1.2 with PLDS-PSK instead of TLS 1.3 with TLS-PSK. Upgrade to a vendor-corrected release after confirming the applicable version guidance for your Tomcat branch.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
21m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-19 21:38Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-19 21:38Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4975",
  "cve_id": "CVE-2026-133325",
  "display_id": "CVE-2026-133325",
  "ghsa_id": "GHSA-j322-r8cv-7j54",
  "euvd_id": "EUVD-2026-130776",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing peer authentication in Apache Tomcat cluster key exchange",
  "summary": "Apache Tomcat 11.0.29, 10.1.62, and 9.0.124 cluster deployments may not authenticate joining peers when using TLS 1.3 with TLS-PSK. An unauthenticated system could join the cluster if that configuration is enabled.",
  "mitigation": "Reconfigure cluster connections to use TLS 1.2 with PLDS-PSK instead of TLS 1.3 with TLS-PSK. Upgrade to a vendor-corrected release after confirming the applicable version guidance for your Tomcat branch.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Tomcat",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 11.0.28, <= 11.0.29",
        "10.1.62",
        "9.0.124"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Apache Tomcat",
      "purl": null
    }
  ],
  "cwes": [
    322
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 21.00365875,
  "t0_at": "2026-11-19T21:38:22.705000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-19T21:38:22.705000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-19T21:38:22.705000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-133325"
    }
  }
}

published 2026-11-19 22:38Z
last change 2026-11-20 06:48Z

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.