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

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

GHSA-42rm-r3mc-w449 ↗

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:eneo < 2.2.0-rc.5
fixed in 2.2.0
CWE-613 Insufficient Session Expiration
ETK-2026-2507Zero's internal tracking ID, independent of the CVE number., no cve assigned
23msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dwaiting for further signals+16d
0
+5d
+10d

description

eneo releases are affected by a session-token lifetime unit mismatch and lack session invalidation after password changes. An attacker who has obtained a valid bearer token can continue using the victim's account after a password change until that token expires; obtaining the token is required first.

mitigation

Upgrade eneo to version 2.2.0. Until upgrades are complete, reduce bearer-token exposure and replace potentially exposed sessions through operational controls.

fixed in 2.2.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
18m
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-07 07:42Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2507",
  "cve_id": null,
  "display_id": "ETK-2026-2507",
  "ghsa_id": "GHSA-42rm-r3mc-w449",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Overlong non-revocable session tokens in eneo",
  "summary": "eneo releases are affected by a session-token lifetime unit mismatch and lack session invalidation after password changes. An attacker who has obtained a valid bearer token can continue using the victim's account after a password change until that token expires; obtaining the token is required first.",
  "mitigation": "Upgrade eneo to version 2.2.0. Until upgrades are complete, reduce bearer-token exposure and replace potentially exposed sessions through operational controls.",
  "vendor": "other",
  "product": "other:eneo",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 2.2.0-rc.5"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "2.2.0"
      ],
      "package_name": "eneo",
      "purl": null
    }
  ],
  "cwes": [
    613
  ],
  "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": 18.360315866666667,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T07:42:56+00:00",
      "days": -15.600072867708333,
      "is_lower_bound": true,
      "measured_at": "2026-10-22T22:07:02.321276+00:00",
      "url": "https://github.com/eneo-ai/eneo/security/advisories/GHSA-42rm-r3mc-w449"
    }
  }
}

published 2026-10-22 21:30Z
last change 2026-10-22 22:05Z

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.