← back to feed
CVE-2026-118539

CVE-2026-118539

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.−1d
Drupal Commerce Core
ETK-2026-2973Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 27msince last run
30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hkev+0hwaiting for further signals+38h25m
0
+12h
+24h
+36h

description

Drupal Commerce Core is identified in the available evidence. The vulnerability type, affected functionality, attacker impact, and conditions required for exploitation are not provided.

mitigation

Apply the remediation or mitigation specified by the Drupal Commerce vendor advisory for this issue. Until that guidance is available or applied, restrict public exposure and access to affected Drupal Commerce Core deployments.

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
30m
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.
−1d

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-28
    vulncheck_kev: trigger signal, started the run
    https://vulncheck.com/cve/CVE-2026-118539
  2. 2026-10-28 00:00Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2973",
  "cve_id": "CVE-2026-118539",
  "display_id": "CVE-2026-118539",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Drupal Commerce Core vulnerability",
  "summary": "Drupal Commerce Core is identified in the available evidence. The vulnerability type, affected functionality, attacker impact, and conditions required for exploitation are not provided.",
  "mitigation": "Apply the remediation or mitigation specified by the Drupal Commerce vendor advisory for this issue. Until that guidance is available or applied, restrict public exposure and access to affected Drupal Commerce Core deployments.",
  "vendor": "Drupal",
  "product": "Commerce Core",
  "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": 29.806561666666667,
  "t0_at": null,
  "signals": {
    "kev": {
      "at": "2026-10-28T00:00:00+00:00",
      "days": -1.6611814758680556,
      "is_lower_bound": true,
      "measured_at": "2026-10-29T15:52:06.160331+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-118539"
    },
    "trigger_signal": {
      "at": "2026-10-28T00:00:00+00:00",
      "days": -1.6611814758680556,
      "is_lower_bound": true,
      "measured_at": "2026-10-29T15:52:06.160331+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-118539"
    }
  }
}

published 2026-10-29 14:02Z
last change 2026-10-29 15:19Z

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.