CVE-2026-125111

validatedZero produced an exploit or a check.

GHSA-5v64-555j-wjxm ↗EUVD-2026-120485 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
rack < 2.2.25; >= 3.0, < 3.1.23; >= 3.2, < 3.2.8
fixed in 2.2.25, 3.1.23, 3.2.8
CWE-400 Uncontrolled Resource Consumption
ETK-2026-4000Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:gem/rack
+30mTTV
9mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal −11dcve.org publicationcheck available+0.0dagent stopped
−10d
−5d

description

Rack versions before 2.2.25, 3.1.23, and 3.2.8 can consume excessive memory when processing multipart requests. An unauthenticated remote attacker may exhaust application worker memory if the application accepts and parses multipart request bodies.

mitigation

Upgrade rack to 2.2.25, 3.1.23, or 3.2.8, as appropriate for the supported release line.

fixed in 2.2.25, 3.1.23, 3.2.8

check
available
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.
–
agent run time
9m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-09 22:02Z
Δ 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 check: a technique exists and was validated, 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-30 02:18Z
  2. 2026-11-09 22:02Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4000",
  "cve_id": "CVE-2026-125111",
  "display_id": "CVE-2026-125111",
  "ghsa_id": "GHSA-5v64-555j-wjxm",
  "euvd_id": "EUVD-2026-120485",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unbounded memory consumption in Rack multipart parsing",
  "summary": "Rack versions before 2.2.25, 3.1.23, and 3.2.8 can consume excessive memory when processing multipart requests. An unauthenticated remote attacker may exhaust application worker memory if the application accepts and parses multipart request bodies.",
  "mitigation": "Upgrade rack to 2.2.25, 3.1.23, or 3.2.8, as appropriate for the supported release line.",
  "vendor": "rack",
  "product": "rack",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 2.2.25"
      ],
      "ecosystem": "rubygems",
      "fixed_versions": [
        "2.2.25"
      ],
      "package_name": "rack",
      "purl": "pkg:gem/rack"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.0, < 3.1.23"
      ],
      "ecosystem": "rubygems",
      "fixed_versions": [
        "3.1.23"
      ],
      "package_name": "rack",
      "purl": "pkg:gem/rack"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.2, < 3.2.8"
      ],
      "ecosystem": "rubygems",
      "fixed_versions": [
        "3.2.8"
      ],
      "package_name": "rack",
      "purl": "pkg:gem/rack"
    }
  ],
  "cwes": [
    400
  ],
  "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 8.73640405,
  "t0_at": "2026-11-09T22:02:38.334000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-09T22:33:00.701290+00:00",
      "days": 0.021092214004629628,
      "is_lower_bound": false,
      "measured_at": "2026-11-09T22:02:38.334000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-30T02:18:55+00:00",
      "days": -10.822029328703703,
      "is_lower_bound": false,
      "measured_at": "2026-11-09T22:02:38.334000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-125111"
    }
  }
}

published 2026-11-09 22:24Z
last change 2026-11-11 06:19Z

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.