← back to feed
CVE-2026-118527

CVE-2026-118527

waiting for further signalsZero needs more public information before it can validate it.
no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.0d
Ivanti Connect Secure
ETK-2026-3102Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 50msince last run
20mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hkev+0hwaiting for further signals+18h32m
0
+6h
+12h

description

The supplied material identifies Ivanti Connect Secure as affected and describes a three-vulnerability attack chain observed in the wild. It does not establish the specific flaw's bug class, attacker capability, or required preconditions.

mitigation

Restrict Ivanti Connect Secure access to trusted networks and monitor for suspicious activity until authoritative remediation guidance is available. The evidence provides no supported fixed version or specific configuration change.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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.
0d

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-30
  2. 2026-10-30 00:00Z
  3. 2026-10-30 00:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3102",
  "cve_id": "CVE-2026-118527",
  "display_id": "CVE-2026-118527",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Ivanti Connect Secure vulnerability with unconfirmed bug class",
  "summary": "The supplied material identifies Ivanti Connect Secure as affected and describes a three-vulnerability attack chain observed in the wild. It does not establish the specific flaw's bug class, attacker capability, or required preconditions.",
  "mitigation": "Restrict Ivanti Connect Secure access to trusted networks and monitor for suspicious activity until authoritative remediation guidance is available. The evidence provides no supported fixed version or specific configuration change.",
  "vendor": "Ivanti",
  "product": "Connect Secure",
  "affected": [],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 20.42355128333333,
  "t0_at": null,
  "signals": {
    "kev": {
      "at": "2026-10-30T00:00:00+00:00",
      "days": -0.8903575105092593,
      "is_lower_bound": true,
      "measured_at": "2026-10-30T21:22:06.919951+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-118527"
    },
    "trigger_signal": {
      "at": "2026-10-30T00:00:00+00:00",
      "days": -0.8903575105092593,
      "is_lower_bound": true,
      "measured_at": "2026-10-30T21:22:06.919951+00:00",
      "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=CVE-2026-118527"
    }
  }
}

published 2026-10-30 18:27Z
last change 2026-10-30 21:04Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.