CVE-2026-85108

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

GHSA-7j7p-grhm-j8xq ↗EUVD-2026-118221 ↗

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.
Apache Software Foundation Apache James Mime4J Core < 0.8.15
fixed in 0.8.15
CWE-770 Allocation of Resources Without Limits or Throttling
ETK-2026-3722Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 12h 40msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h43m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Apache James Mime4J Core and DOM versions before 0.8.15 can consume excessive resources while parsing MIME messages. An attacker may cause a denial of service when the application processes attacker-controlled MIME content.

mitigation

Upgrade org.apache.james:apache-mime4j-core and org.apache.james:apache-mime4j-dom to version 0.8.15 or later.

fixed in 0.8.15

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
9m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-06 11: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-06 11:46Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3722",
  "cve_id": "CVE-2026-85108",
  "display_id": "CVE-2026-85108",
  "ghsa_id": "GHSA-7j7p-grhm-j8xq",
  "euvd_id": "EUVD-2026-118221",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unbounded resource allocation in Apache James Mime4J",
  "summary": "Apache James Mime4J Core and DOM versions before 0.8.15 can consume excessive resources while parsing MIME messages. An attacker may cause a denial of service when the application processes attacker-controlled MIME content.",
  "mitigation": "Upgrade org.apache.james:apache-mime4j-core and org.apache.james:apache-mime4j-dom to version 0.8.15 or later.",
  "vendor": "Apache Software Foundation",
  "product": "Apache James Mime4J Core",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.8.15"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.8.15"
      ],
      "package_name": "org.apache.james:apache-mime4j-core",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.8.15"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.8.15"
      ],
      "package_name": "org.apache.james:apache-mime4j-dom",
      "purl": null
    }
  ],
  "cwes": [
    770
  ],
  "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": 9.168594566666666,
  "t0_at": "2026-11-06T11:46:28.639000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-06T11:46:28.639000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-06T11:46:28.639000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-85108"
    }
  }
}

published 2026-11-06 12:20Z
last change 2026-11-08 00:40Z

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.