ETK-2026-718Zero's internal tracking ID, independent of the CVE number.

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

GHSA-p6pm-ch9v-44vx ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
rubygems:dalli < 3.2.12; >= 4.0.0, < 4.3.6; >= 5.0.0, < 5.0.9; >= 5.1.0, < 5.1.3; >= 5.2.0, < 5.2.1
fixed in 3.2.12, 4.3.6, 5.0.9, 5.1.3, 5.2.1
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
ETK-2026-718, no cve assigned
pkg:gem/dalli
cvss7.0ethiack provisional
15d 14h 45msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
waiting for further signals−0.1dtrigger signal +0d
+5d
+10d
+15d

description

Affected dalli releases can lose reply synchronization after memcached rejects an oversized cache key, allowing later reads on a shared connection to receive data cached under another key. An attacker needs influence over part of a cache key and an application path using the affected multi-key operations; applications using per-user cached data may expose one user's cached content to another. Releases before 5.0 using the binary protocol can instead cause requests to stall when given such a key.

mitigation

Upgrade dalli to 3.2.12, 4.3.6, 5.0.9, 5.1.3, or 5.2.1, as appropriate for the deployed branch. Until upgraded, prevent untrusted input from contributing to cache keys and enforce the memcached key-size limit after encoding.

fixed in 3.2.12, 4.3.6, 5.0.9, 5.1.3, 5.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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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-05 22:28Z

this entry in the feed

GET /api/v1/feed/ETK-2026-718

{
  "etk_id": "ETK-2026-718",
  "cve_id": null,
  "display_id": "ETK-2026-718",
  "ghsa_id": "GHSA-p6pm-ch9v-44vx",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Cross-key cache value exposure in dalli reply parsing",
  "summary": "Affected dalli releases can lose reply synchronization after memcached rejects an oversized cache key, allowing later reads on a shared connection to receive data cached under another key. An attacker needs influence over part of a cache key and an application path using the affected multi-key operations; applications using per-user cached data may expose one user's cached content to another. Releases before 5.0 using the binary protocol can instead cause requests to stall when given such a key.",
  "mitigation": "Upgrade dalli to 3.2.12, 4.3.6, 5.0.9, 5.1.3, or 5.2.1, as appropriate for the deployed branch. Until upgraded, prevent untrusted input from contributing to cache keys and enforce the memcached key-size limit after encoding.",
  "vendor": "rubygems",
  "product": "rubygems:dalli",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 3.2.12"
      ],
      "ecosystem": "rubygems",
      "fixed_versions": [
        "3.2.12"
      ],
      "package_name": "dalli",
      "purl": "pkg:gem/dalli"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.0.0, < 4.3.6"
      ],
      "ecosystem": "rubygems",
      "fixed_versions": [
        "4.3.6"
      ],
      "package_name": "dalli",
      "purl": "pkg:gem/dalli"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 5.0.0, < 5.0.9"
      ],
      "ecosystem": "rubygems",
      "fixed_versions": [
        "5.0.9"
      ],
      "package_name": "dalli",
      "purl": "pkg:gem/dalli"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 5.1.0, < 5.1.3"
      ],
      "ecosystem": "rubygems",
      "fixed_versions": [
        "5.1.3"
      ],
      "package_name": "dalli",
      "purl": "pkg:gem/dalli"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 5.2.0, < 5.2.1"
      ],
      "ecosystem": "rubygems",
      "fixed_versions": [
        "5.2.1"
      ],
      "package_name": "dalli",
      "purl": "pkg:gem/dalli"
    }
  ],
  "cwes": [
    200
  ],
  "cvss_score": 7,
  "cvss_src": "ethiack_provisional",
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 16.075738683333334,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-05T22:28:41+00:00",
      "days": -15.541691686053241,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T11:28:43.216714+00:00",
      "url": "https://github.com/petergoldstein/dalli/security/advisories/GHSA-p6pm-ch9v-44vx"
    }
  }
}

published 2026-10-06 02:56Z
last change 2026-10-21 11:18Z

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.