CVE-2026-110938

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

GHSA-vj95-43qj-j5mf ↗EUVD-2026-107139 ↗

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-125 Out-of-bounds Read
ETK-2026-2303Zero's internal tracking ID, independent of the CVE number., permanent identifier
32msince last run
1h 31mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+2h22m
0
+4h
+6h
+8h
+10h
+12h

description

Eclipse OpenJ9 JITServer protocol handling can mishandle message boundaries and terminate a JITServer daemon or connected client JVM. An unauthenticated attacker can cause denial of service by sending malformed traffic when they can reach a JITServer endpoint; a malicious JITServer can likewise affect its clients.

mitigation

Upgrade Eclipse OpenJ9 to version 0.63. Until upgrading, restrict JITServer network access to trusted hosts and networks.

fixed in 0.63

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.
–
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 31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 08:03Z
Δ 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

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.

  1. 2026-10-21 08:03Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2303",
  "cve_id": "CVE-2026-110938",
  "display_id": "CVE-2026-110938",
  "ghsa_id": "GHSA-vj95-43qj-j5mf",
  "euvd_id": "EUVD-2026-107139",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper bounds checking in Eclipse OpenJ9 JITServer",
  "summary": "Eclipse OpenJ9 JITServer protocol handling can mishandle message boundaries and terminate a JITServer daemon or connected client JVM. An unauthenticated attacker can cause denial of service by sending malformed traffic when they can reach a JITServer endpoint; a malicious JITServer can likewise affect its clients.",
  "mitigation": "Upgrade Eclipse OpenJ9 to version 0.63. Until upgrading, restrict JITServer network access to trusted hosts 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": [
    125
  ],
  "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": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 91.35564908333333,
  "t0_at": "2026-10-21T08:03:26.062000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T08:03:26.062000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T08:03:26.062000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110938"
    }
  }
}

published 2026-10-21 08:53Z
last change 2026-10-21 10:46Z

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.