CVE-2026-13575

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

GHSA-6f9x-5fgh-99f6 ↗EUVD-2026-114833 ↗

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.
http-session < 0.54
fixed in 0.54
CWE-93 Improper Neutralization of CRLF Sequences ('CRLF Injection')
ETK-2026-3225Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 43msince last run
28mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h49m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

HTTP::Session versions before 0.54 are affected when HTTP::Session::Store::CHI is configured with a memcached-backed driver. An attacker able to supply a crafted session cookie identifier may cause additional commands to be processed by the memcached server.

mitigation

Upgrade http-session to version 0.54 or later. Until upgraded, avoid using a memcached driver with HTTP::Session::Store::CHI and restrict access to the memcached service.

fixed in 0.54

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
28m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-01 10:46Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-01 10:46Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3225",
  "cve_id": "CVE-2026-13575",
  "display_id": "CVE-2026-13575",
  "ghsa_id": "GHSA-6f9x-5fgh-99f6",
  "euvd_id": "EUVD-2026-114833",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Memcached command injection in HTTP::Session CHI store",
  "summary": "HTTP::Session versions before 0.54 are affected when HTTP::Session::Store::CHI is configured with a memcached-backed driver. An attacker able to supply a crafted session cookie identifier may cause additional commands to be processed by the memcached server.",
  "mitigation": "Upgrade http-session to version 0.54 or later. Until upgraded, avoid using a memcached driver with HTTP::Session::Store::CHI and restrict access to the memcached service.",
  "vendor": null,
  "product": "http-session",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.54"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.54"
      ],
      "package_name": "http-session",
      "purl": null
    }
  ],
  "cwes": [
    93
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 27.6319894,
  "t0_at": "2026-11-01T10:46:36.389000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-01T10:46:36.389000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-01T10:46:36.389000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-13575"
    }
  }
}

published 2026-11-01 11:08Z
last change 2026-11-01 13:00Z

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.