CVE-2026-111594

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

EUVD-2026-108523 ↗

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.
InterSystems IRIS for Health 2026.2.0.221; 2026.1.0.235; 2025.3.0.226
CWE-319 Cleartext Transmission of Sensitive Information
ETK-2026-2515Zero's internal tracking ID, independent of the CVE number., permanent identifier
31msince last run
30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h26m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

InterSystems IRIS for Health is affected when its default configuration leaves TLS/SSL encryption disabled. An attacker able to observe relevant network traffic may read transmitted data and potentially use it to access the device.

mitigation

Enable and require TLS/SSL for affected IRIS for Health communications, and restrict access to trusted networks until encrypted transport is verified. No fixed version is recorded in the supplied advisory data.

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
30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 21:39Z
Δ 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-22 21:39Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2515",
  "cve_id": "CVE-2026-111594",
  "display_id": "CVE-2026-111594",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-108523",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cleartext transport default in InterSystems IRIS for Health",
  "summary": "InterSystems IRIS for Health is affected when its default configuration leaves TLS/SSL encryption disabled. An attacker able to observe relevant network traffic may read transmitted data and potentially use it to access the device.",
  "mitigation": "Enable and require TLS/SSL for affected IRIS for Health communications, and restrict access to trusted networks until encrypted transport is verified. No fixed version is recorded in the supplied advisory data.",
  "vendor": "InterSystems",
  "product": "IRIS for Health",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "2026.2.0.221",
        "2026.1.0.235",
        "2025.3.0.226"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "IRIS for Health",
      "purl": null
    }
  ],
  "cwes": [
    319
  ],
  "cvss_score": 9.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/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": 29.557104166666665,
  "t0_at": "2026-10-22T21:39:47.105000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T21:39:47.105000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T21:39:47.105000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111594"
    }
  }
}

published 2026-10-22 22:35Z
last change 2026-10-22 23:05Z

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.