CVE-2026-111074

validatingZero is analyzing and reversing it now.

GHSA-rr74-gf97-xpw7 ↗EUVD-2026-107134 ↗

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.
Eclipse Foundation Eclipse OpenJ9 >= 0.8.0, < 0.63
fixed in 0.63
CWE-190 Integer Overflow or Wraparound
ETK-2026-2300Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 23mrunning
synthesiscurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0hvalidating
0
+1h
+2h

description

Eclipse OpenJ9 JITServer releases before 0.63 are affected by a remote denial-of-service flaw. An unauthenticated attacker able to reach the JITServer TCP service can consume compilation worker threads, disrupting compilation for connected JVMs.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade Eclipse OpenJ9 to version 0.63 or later. Until upgraded, restrict JITServer TCP access to trusted clients and networks.

fixed in 0.63

check
building now
exploit
not yet
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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 23m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 07:57Z
Δ 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

Run in progress: no artifact yet.

source signals

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

  1. 2026-10-21 07:57Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2300",
  "cve_id": "CVE-2026-111074",
  "display_id": "CVE-2026-111074",
  "ghsa_id": "GHSA-rr74-gf97-xpw7",
  "euvd_id": "EUVD-2026-107134",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Pre-authentication denial of service in Eclipse OpenJ9 JITServer",
  "summary": "Eclipse OpenJ9 JITServer releases before 0.63 are affected by a remote denial-of-service flaw. An unauthenticated attacker able to reach the JITServer TCP service can consume compilation worker threads, disrupting compilation for connected JVMs.",
  "mitigation": "Upgrade Eclipse OpenJ9 to version 0.63 or later. Until upgraded, restrict JITServer TCP access to trusted clients and networks.",
  "vendor": "Eclipse Foundation",
  "product": "Eclipse OpenJ9",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.8.0, < 0.63"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.63"
      ],
      "package_name": "Eclipse OpenJ9",
      "purl": null
    }
  ],
  "cwes": [
    190
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-10-21T07:57:16.912000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T07:57:16.912000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T07:57:16.912000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111074"
    }
  }
}

published 2026-10-21 08:26Z
last change 2026-10-21 09:43Z

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.