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

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

GHSA-qjjc-q2h2-56cg ↗

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:beenuar/AiSOC <= 16.0.1
fixed in 17.0.0
CWE-287 Improper Authentication
ETK-2026-640, no cve assigned
13d 18h 38msince last run
28mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −16dwaiting for further signals−14d
−15d
−10d
−5d
0

description

AiSOC versions before 17.0.0 can associate an OIDC login with an existing local account using an email claim that has not been verified. An attacker may gain access as that account, including its assigned permissions, when the configured identity provider permits an authenticated user to present a matching unverified email address.

mitigation

Upgrade AiSOC to version 17.0.0. Until upgrading, configure the identity provider to issue only verified email claims and restrict or disable OIDC sign-in where that cannot be enforced.

fixed in 17.0.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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
28m
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 09:03Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-640",
  "cve_id": null,
  "display_id": "ETK-2026-640",
  "ghsa_id": "GHSA-qjjc-q2h2-56cg",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Improper OIDC account binding in AiSOC",
  "summary": "AiSOC versions before 17.0.0 can associate an OIDC login with an existing local account using an email claim that has not been verified. An attacker may gain access as that account, including its assigned permissions, when the configured identity provider permits an authenticated user to present a matching unverified email address.",
  "mitigation": "Upgrade AiSOC to version 17.0.0. Until upgrading, configure the identity provider to issue only verified email claims and restrict or disable OIDC sign-in where that cannot be enforced.",
  "vendor": "other",
  "product": "other:beenuar/AiSOC",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 16.0.1"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "17.0.0"
      ],
      "package_name": "beenuar/AiSOC",
      "purl": null
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 7.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 27.73997795,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-05T09:03:41+00:00",
      "days": -15.86366689761574,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T05:47:21.842760+00:00",
      "url": "https://github.com/beenuar/AiSOC/security/advisories/GHSA-qjjc-q2h2-56cg"
    }
  }
}

published 2026-10-05 10:10Z
last change 2026-10-21 05:31Z

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.