CVE-2026-107908

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

GHSA-jpx9-94mp-7xhq ↗EUVD-2026-95485 ↗

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.
FalkorDB < 4.20.0
fixed in 4.20.0
CWE-787 Out-of-bounds Write
ETK-2026-1049Zero's internal tracking ID, independent of the CVE number., permanent identifier
11d 23h 45msince last run
8mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h52m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

FalkorDB versions before 4.20.0 contain a heap out-of-bounds write in handling of Bolt protocol messages. A remote unauthenticated attacker may disrupt the service and could potentially execute code, but only where the optional Bolt endpoint is enabled.

mitigation

Upgrade FalkorDB to version 4.20.0 or later. Disable the Bolt endpoint by removing or disabling BOLT_PORT where Bolt access is not required.

fixed in 4.20.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.
–
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.
0.60%47th percentile
agent run time
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-09 05:08Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-09 05:08Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1049",
  "cve_id": "CVE-2026-107908",
  "display_id": "CVE-2026-107908",
  "ghsa_id": "GHSA-jpx9-94mp-7xhq",
  "euvd_id": "EUVD-2026-95485",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated heap out-of-bounds write in FalkorDB Bolt endpoint",
  "summary": "FalkorDB versions before 4.20.0 contain a heap out-of-bounds write in handling of Bolt protocol messages. A remote unauthenticated attacker may disrupt the service and could potentially execute code, but only where the optional Bolt endpoint is enabled.",
  "mitigation": "Upgrade FalkorDB to version 4.20.0 or later. Disable the Bolt endpoint by removing or disabling BOLT_PORT where Bolt access is not required.",
  "vendor": "FalkorDB",
  "product": "FalkorDB",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 4.20.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.20.0"
      ],
      "package_name": "FalkorDB",
      "purl": null
    }
  ],
  "cwes": [
    787
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.006,
  "epss_percentile": 0.4749,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 8.359432983333333,
  "t0_at": "2026-10-09T05:08:06.419000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-09T05:08:06.419000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T05:08:06.419000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-107908"
    }
  }
}

published 2026-10-09 05:51Z
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.