CVE-2026-80298

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

GHSA-4fxr-7rqw-6ppg ↗EUVD-2026-91329 ↗

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.
HAVELSAN Inc. Sef - AI Chatbot Platform < 2.1
fixed in 2.1
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-325, permanent identifier
18d 14h 27msince last run
33mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+5h14m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Sef - AI Chatbot Platform versions earlier than 2.1 are affected by an SQL injection vulnerability. An attacker may be able to alter database queries through a vulnerable application input; the advisory does not specify the affected interface or authentication precondition.

mitigation

Upgrade Sef - AI Chatbot Platform to version 2.1 or later. Until upgrades are complete, restrict access to the platform to trusted users and networks.

fixed in 2.1

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-325",
  "cve_id": "CVE-2026-80298",
  "display_id": "CVE-2026-80298",
  "ghsa_id": "GHSA-4fxr-7rqw-6ppg",
  "euvd_id": "EUVD-2026-91329",
  "status": "published",
  "anchor_state": "anchored",
  "title": "SQL injection in Sef - AI Chatbot Platform",
  "summary": "Sef - AI Chatbot Platform versions earlier than 2.1 are affected by an SQL injection vulnerability. An attacker may be able to alter database queries through a vulnerable application input; the advisory does not specify the affected interface or authentication precondition.",
  "mitigation": "Upgrade Sef - AI Chatbot Platform to version 2.1 or later. Until upgrades are complete, restrict access to the platform to trusted users and networks.",
  "vendor": "HAVELSAN Inc.",
  "product": "Sef - AI Chatbot Platform",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.1"
      ],
      "package_name": "Sef - AI Chatbot Platform",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.003,
  "epss_percentile": 0.2079,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 32.69090675,
  "t0_at": "2026-10-02T09:07:52.553000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T09:07:52.553000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-02T09:07:52.553000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-80298"
    }
  }
}

published 2026-10-02 10:44Z
last change 2026-10-21 04:45Z

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.