ETK-2026-717Zero's internal tracking ID, independent of the CVE number.

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

GHSA-w2jh-h3pq-273j ↗

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.
other / arkime / wise:idaholab/Malcolm < 26.09.0
fixed in 26.10.0
CWE-798 Use of Hard-coded Credentials
ETK-2026-717, no cve assigned
15d 15h 45msince last run
34mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
waiting for further signals−16dtrigger signal −16d
−10d
−5d
0

description

Malcolm deployments using Arkime WISE may retain a publicly known PIN for WISE configuration changes. An attacker who can reach the enabled WISE interface and satisfy other access controls could alter enrichment settings, potentially affecting lookup behavior and investigation results.

mitigation

Upgrade Malcolm to version 26.10.0. Replace any example WISE PIN with a unique secret, and disable or restrict access to WISE where it is not required.

fixed in 26.10.0

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.
–
agent run time
34m
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.
–

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-05 21:19Z

this entry in the feed

GET /api/v1/feed/ETK-2026-717

{
  "etk_id": "ETK-2026-717",
  "cve_id": null,
  "display_id": "ETK-2026-717",
  "ghsa_id": "GHSA-w2jh-h3pq-273j",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Default configuration PIN in Malcolm Arkime WISE",
  "summary": "Malcolm deployments using Arkime WISE may retain a publicly known PIN for WISE configuration changes. An attacker who can reach the enabled WISE interface and satisfy other access controls could alter enrichment settings, potentially affecting lookup behavior and investigation results.",
  "mitigation": "Upgrade Malcolm to version 26.10.0. Replace any example WISE PIN with a unique secret, and disable or restrict access to WISE where it is not required.",
  "vendor": "other / arkime / wise",
  "product": "other / arkime / wise:idaholab/Malcolm",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 26.09.0"
      ],
      "ecosystem": "other / arkime / wise",
      "fixed_versions": [
        "26.10.0"
      ],
      "package_name": "idaholab/Malcolm",
      "purl": null
    }
  ],
  "cwes": [
    798
  ],
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 33.89525855,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-05T21:19:11+00:00",
      "days": -15.590298842280093,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T11:29:12.843072+00:00",
      "url": "https://github.com/cisagov/Malcolm/security/advisories/GHSA-w2jh-h3pq-273j"
    }
  }
}

published 2026-10-06 02:36Z
last change 2026-10-21 11:18Z

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.