CVE-2026-93886

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

GHSA-mj4j-q283-wr2g ↗EUVD-2026-98177 ↗

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.
IBM i 7.6; 7.5; 7.4; 7.3
CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
ETK-2026-1437Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 04h 20msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h06m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

IBM i versions 7.3, 7.4, 7.5, and 7.6 are affected by improper validation of user-supplied input. A remote attacker with valid authentication may be able to execute arbitrary script code.

mitigation

Restrict remote access to trusted, authenticated users and limit accounts to the minimum required privileges. Monitor IBM security updates and apply the vendor-provided fix when it becomes available.

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.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.19%7th percentile
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 23:22Z
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-12 23:22Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1437",
  "cve_id": "CVE-2026-93886",
  "display_id": "CVE-2026-93886",
  "ghsa_id": "GHSA-mj4j-q283-wr2g",
  "euvd_id": "EUVD-2026-98177",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper input validation in IBM i",
  "summary": "IBM i versions 7.3, 7.4, 7.5, and 7.6 are affected by improper validation of user-supplied input. A remote attacker with valid authentication may be able to execute arbitrary script code.",
  "mitigation": "Restrict remote access to trusted, authenticated users and limit accounts to the minimum required privileges. Monitor IBM security updates and apply the vendor-provided fix when it becomes available.",
  "vendor": "IBM",
  "product": "i",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "7.6",
        "7.5",
        "7.4",
        "7.3"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "i",
      "purl": null
    }
  ],
  "cwes": [
    79
  ],
  "cvss_score": 8.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:L",
  "epss_score": 0.0019,
  "epss_percentile": 0.0778,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.157172116666667,
  "t0_at": "2026-10-12T23:22:16.102000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T23:22:16.102000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T23:22:16.102000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-93886"
    }
  }
}

published 2026-10-13 00:16Z
last change 2026-10-21 04:45Z

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.