CVE-2026-5759

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

GHSA-gxrc-33jm-h5ch ↗EUVD-2026-95473 ↗

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.18.1
fixed in 4.18.1
CWE-415 Double Free
ETK-2026-1043Zero's internal tracking ID, independent of the CVE number., permanent identifier
11d 22h 14msince last run
38mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h28m
0
+2h
+6h
+8h
+10h
+12h

description

FalkorDB versions before 4.18.1 contain a memory-management flaw in RDB graph decoding. An attacker who can issue Redis replication commands may cause a denial of service or execute code in the redis-server process.

mitigation

Upgrade FalkorDB to version 4.18.1 or later. Restrict Redis replication commands to authenticated, trusted clients and do not expose them to untrusted networks.

fixed in 4.18.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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.55%45th percentile
agent run time
38m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-09 04:04Z
Δ 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-09 04:04Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1043",
  "cve_id": "CVE-2026-5759",
  "display_id": "CVE-2026-5759",
  "ghsa_id": "GHSA-gxrc-33jm-h5ch",
  "euvd_id": "EUVD-2026-95473",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Double-free use-after-free in FalkorDB RDB graph decoder",
  "summary": "FalkorDB versions before 4.18.1 contain a memory-management flaw in RDB graph decoding. An attacker who can issue Redis replication commands may cause a denial of service or execute code in the redis-server process.",
  "mitigation": "Upgrade FalkorDB to version 4.18.1 or later. Restrict Redis replication commands to authenticated, trusted clients and do not expose them to untrusted networks.",
  "vendor": "FalkorDB",
  "product": "FalkorDB",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 4.18.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.18.1"
      ],
      "package_name": "FalkorDB",
      "purl": null
    }
  ],
  "cwes": [
    415
  ],
  "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.0055,
  "epss_percentile": 0.4518,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 37.82181995,
  "t0_at": "2026-10-09T04:04:28.078000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-09T04:04:28.078000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T04:04:28.078000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-5759"
    }
  }
}

published 2026-10-09 04:46Z
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.