CVE-2026-114138

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

GHSA-33wh-fxxf-88vv ↗EUVD-2026-107548 ↗

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.
encode django-rest-framework <= 3.18.0
fixed in 3.18.2
CWE-400 Uncontrolled Resource Consumption
ETK-2026-2358Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/djangorestframework
2h 21msince last run
8mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h03m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Django REST framework versions before 3.18.2 can spend excessive CPU processing oversized, token-heavy Accept headers. An unauthenticated remote client can degrade availability by sending such requests to reachable API endpoints, particularly where synchronous workers handle concurrent traffic.

mitigation

Upgrade django-rest-framework to version 3.18.2 or later. Until upgraded, limit request-header sizes and rate-limit unauthenticated requests at the proxy or application edge.

fixed in 3.18.2

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.
–
agent run time
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 20:09Z
Δ 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-21 20:09Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2358",
  "cve_id": "CVE-2026-114138",
  "display_id": "CVE-2026-114138",
  "ghsa_id": "GHSA-33wh-fxxf-88vv",
  "euvd_id": "EUVD-2026-107548",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Accept header CPU exhaustion in django-rest-framework",
  "summary": "Django REST framework versions before 3.18.2 can spend excessive CPU processing oversized, token-heavy Accept headers. An unauthenticated remote client can degrade availability by sending such requests to reachable API endpoints, particularly where synchronous workers handle concurrent traffic.",
  "mitigation": "Upgrade django-rest-framework to version 3.18.2 or later. Until upgraded, limit request-header sizes and rate-limit unauthenticated requests at the proxy or application edge.",
  "vendor": "encode",
  "product": "django-rest-framework",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 3.18.0"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "3.18.2"
      ],
      "package_name": "djangorestframework",
      "purl": "pkg:pypi/djangorestframework"
    }
  ],
  "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": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 8.11851225,
  "t0_at": "2026-10-21T20:09:06.489000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T20:09:06.489000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T20:09:06.489000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-114138"
    }
  }
}

published 2026-10-21 21:04Z
last change 2026-10-21 22:34Z

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.