CVE-2026-107202

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

GHSA-qrj2-qqx7-wqxq ↗EUVD-2026-94361 ↗

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.
jonssonyan h-ui 0.0.25
CWE-77 Improper Neutralization of Special Elements used in a Command ('Command Injection')
ETK-2026-1330Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 20h 01msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+114h21m
0
+2h
+4h
+6h
+8h
+10h

description

h-ui versions 0.0.25 and earlier inadequately validate the administrative API's listen configuration. An authenticated administrator able to change that setting may execute operating-system commands with root privileges.

mitigation

Restrict administrative API access to trusted administrators and prevent changes to the listen configuration on affected installations. Upgrade when a vendor-fixed release is available; no fixed version is identified in the evidence.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.78%55th percentile
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 14:26Z
Δ 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-07 14:26Z
    ghsa: trigger signal, started the run
  2. 2026-10-07 14:26Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1330",
  "cve_id": "CVE-2026-107202",
  "display_id": "CVE-2026-107202",
  "ghsa_id": "GHSA-qrj2-qqx7-wqxq",
  "euvd_id": "EUVD-2026-94361",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Command injection in h-ui administrative API",
  "summary": "h-ui versions 0.0.25 and earlier inadequately validate the administrative API's listen configuration. An authenticated administrator able to change that setting may execute operating-system commands with root privileges.",
  "mitigation": "Restrict administrative API access to trusted administrators and prevent changes to the listen configuration on affected installations. Upgrade when a vendor-fixed release is available; no fixed version is identified in the evidence.",
  "vendor": "jonssonyan",
  "product": "h-ui",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "0.0.25"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "h-ui",
      "purl": null
    }
  ],
  "cwes": [
    77
  ],
  "cvss_score": 9.1,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.0078,
  "epss_percentile": 0.551,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.516758216666666,
  "t0_at": "2026-10-07T14:26:49.905000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T14:26:49.905000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T14:26:49.905000+00:00",
      "url": "https://github.com/advisories/GHSA-qrj2-qqx7-wqxq"
    }
  }
}

published 2026-10-12 08:29Z
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.