CVE-2026-111279

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

GHSA-w5x4-fq2q-m366 ↗EUVD-2026-102470 ↗

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.
dragonflydb dragonfly <= 2.0.2
ETK-2026-1882Zero's internal tracking ID, independent of the CVE number., permanent identifier
3d 23h 36msince last run
1h 58mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+41h21m
0
+2h
+4h
+6h
+8h
+10h

description

Dragonfly through 2.0.2 is affected by uncontrolled memory allocation in random-member commands that accept a count value. An unauthenticated client with network access to the service can consume available memory and cause the Dragonfly instance to terminate.

mitigation

Upgrade Dragonfly to a release newer than 2.0.2. Until upgraded, restrict network access so untrusted clients cannot connect to the service.

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.49%40th percentile
agent run time
1h 58m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 21:43Z
Δ 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-15 21:43Z
    ghsa: trigger signal, started the run
  2. 2026-10-15 21:43Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1882",
  "cve_id": "CVE-2026-111279",
  "display_id": "CVE-2026-111279",
  "ghsa_id": "GHSA-w5x4-fq2q-m366",
  "euvd_id": "EUVD-2026-102470",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unbounded memory allocation in Dragonfly random-member commands",
  "summary": "Dragonfly through 2.0.2 is affected by uncontrolled memory allocation in random-member commands that accept a count value. An unauthenticated client with network access to the service can consume available memory and cause the Dragonfly instance to terminate.",
  "mitigation": "Upgrade Dragonfly to a release newer than 2.0.2. Until upgraded, restrict network access so untrusted clients cannot connect to the service.",
  "vendor": "dragonflydb",
  "product": "dragonfly",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.0.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "dragonfly",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0049,
  "epss_percentile": 0.4048,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 117.74639115,
  "t0_at": "2026-10-15T21:43:23.862000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T21:43:23.862000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T21:43:23.862000+00:00",
      "url": "https://github.com/advisories/GHSA-w5x4-fq2q-m366"
    }
  }
}

published 2026-10-17 13:06Z
last change 2026-10-21 13:29Z

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.