CVE-2026-66246

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

GHSA-3hwm-64f6-4634 ↗EUVD-2026-90813 ↗

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.
HCL Software iControl v4.5.0
CWE-250 Execution with Unnecessary Privileges
ETK-2026-244, permanent identifier
20d 00h 57msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h16m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

iControl deployments may fail to enforce authorization checks for some application resources. An attacker able to reach an affected interface could gain elevated privileges or change or remove sensitive application data where those checks are missing.

mitigation

Restrict iControl access to trusted, authenticated users and networks, and apply least-privilege permissions. Monitor HCL updates and apply a vendor-provided fix when one is released; no fixed version is recorded.

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, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.30%21st percentile
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 13:23Z
Δ 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-01 13:23Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-244",
  "cve_id": "CVE-2026-66246",
  "display_id": "CVE-2026-66246",
  "ghsa_id": "GHSA-3hwm-64f6-4634",
  "euvd_id": "EUVD-2026-90813",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Broken access control in iControl",
  "summary": "iControl deployments may fail to enforce authorization checks for some application resources. An attacker able to reach an affected interface could gain elevated privileges or change or remove sensitive application data where those checks are missing.",
  "mitigation": "Restrict iControl access to trusted, authenticated users and networks, and apply least-privilege permissions. Monitor HCL updates and apply a vendor-provided fix when one is released; no fixed version is recorded.",
  "vendor": "HCL Software",
  "product": "iControl",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "v4.5.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "iControl",
      "purl": null
    }
  ],
  "cwes": [
    250
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.003,
  "epss_percentile": 0.2179,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.236797033333332,
  "t0_at": "2026-10-01T13:23:25.586000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T13:23:25.586000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T13:23:25.586000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-66246"
    }
  }
}

published 2026-10-01 14:19Z
last change 2026-10-21 12:26Z

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.