CVE-2026-94249

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

GHSA-x7mj-p5qg-3rcg ↗EUVD-2026-119878 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
TÜBİTAK BİLGEM Software Technologies Research Institute Liderahenk < 2.0.3
fixed in 2.0.3
CWE-862 Missing Authorization
ETK-2026-3936Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 22h 04msince last run
30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h35m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Liderahenk versions earlier than 2.0.3 have an authorization-control flaw. An attacker who can access affected functionality may gain privileges beyond those intended.

mitigation

Upgrade Liderahenk to version 2.0.3 or later. Restrict access to Liderahenk functions to trusted users and networks until the upgrade is complete.

fixed in 2.0.3

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.
0.25%16th percentile
agent run time
30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-09 08:20Z
Δ 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, 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-11-09 08:20Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3936",
  "cve_id": "CVE-2026-94249",
  "display_id": "CVE-2026-94249",
  "ghsa_id": "GHSA-x7mj-p5qg-3rcg",
  "euvd_id": "EUVD-2026-119878",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authorization in Liderahenk",
  "summary": "Liderahenk versions earlier than 2.0.3 have an authorization-control flaw. An attacker who can access affected functionality may gain privileges beyond those intended.",
  "mitigation": "Upgrade Liderahenk to version 2.0.3 or later. Restrict access to Liderahenk functions to trusted users and networks until the upgrade is complete.",
  "vendor": "TÜBİTAK BİLGEM Software Technologies Research Institute",
  "product": "Liderahenk",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2.0.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.0.3"
      ],
      "package_name": "Liderahenk",
      "purl": null
    }
  ],
  "cwes": [
    862
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.0025,
  "epss_percentile": 0.1691,
  "epss_asof": "2026-11-09",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 30.471763533333334,
  "t0_at": "2026-11-09T08:20:47.815000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-09T08:20:47.815000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-09T08:20:47.815000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-94249"
    }
  }
}

published 2026-11-09 08:25Z
last change 2026-11-11 06:34Z

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.