CVE-2026-108515

waiting for further signals

no check availablenot proven exploitable

awaiting cvepublic pockev

Drupal core

ETK-2026-1989, permanent identifier

cvss4.0ethiack provisional

3d 04h 47msince last run

1h 06mAI analysis

timeline

0 = cve.org, not yet published

trigger signal −6.4dwaiting for further signals−3.2d

−6d

−4d

−2d

description

Drupal core's Link module is affected by a cross-site scripting issue involving Link fields. An attacker who can edit an affected field may cause script to execute in another user's browser when insufficiently sanitized content is rendered.

mitigation

Restrict permissions to edit affected Link fields to trusted users and review where those fields are rendered. Apply Drupal's vendor update when a fixed release is identified for the deployed branch.

check

exploit

automation

contextual

auth required

–

EPSS

–

agent run time

1h 06m

cve.org record, t = 0

not published yet

Δ to public poc

–

Δ to kev

–

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.

2026-10-15 12:07Z
thehackernews: trigger signal, started the run
https://thehackernews.com/2026/10/drupal-patches-critical-core-rce-flaw.html
2026-10-15 12:07Z
Drupal Patches Critical Field UI Flaw With Unauthenticated RCE Path via Contributed Modules
thehackernews · https://thehackernews.com/2026/10/drupal-patches-critical-core-rce-flaw.html

this entry in the feed

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

{
  "etk_id": "ETK-2026-1989",
  "cve_id": "CVE-2026-108515",
  "display_id": "CVE-2026-108515",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Cross-site scripting in Drupal core Link module",
  "summary": "Drupal core's Link module is affected by a cross-site scripting issue involving Link fields. An attacker who can edit an affected field may cause script to execute in another user's browser when insufficiently sanitized content is rendered.",
  "mitigation": "Restrict permissions to edit affected Link fields to trusted users and review where those fields are rendered. Apply Drupal's vendor update when a fixed release is identified for the deployed branch.",
  "vendor": "Drupal",
  "product": "Drupal core",
  "affected": [],
  "cwes": null,
  "cvss_score": 4,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 65.73918125,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T12:07:20+00:00",
      "days": -6.359452072766204,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T20:44:56.734438+00:00",
      "url": "https://thehackernews.com/2026/10/drupal-patches-critical-core-rce-flaw.html"
    }
  }
}

published 2026-10-18 15:53Z
last change 2026-10-21 20: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.