CVE-2026-108089

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

GHSA-fv7w-gq56-762w ↗EUVD-2026-104914 ↗

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 Cocoon <= *
CWE-497 Exposure of Sensitive System Information to an Unauthorized Control Sphere
ETK-2026-2159Zero's internal tracking ID, independent of the CVE number., permanent identifier
19h 38msince last run
1h 30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+6h16m
0
+2h
+4h
+8h
+10h
+12h

description

All Apache Cocoon versions allow unauthenticated access to diagnostic interfaces. An attacker who can reach an affected instance may view verbose diagnostic or profiling information and invoke cache-related functions.

mitigation

Restrict the Cocoon instance and its diagnostic interfaces to trusted users and networks. Plan to replace Apache Cocoon, as no fixed version is planned.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-20 10:25Z
Δ 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-20 10:25Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2159",
  "cve_id": "CVE-2026-108089",
  "display_id": "CVE-2026-108089",
  "ghsa_id": "GHSA-fv7w-gq56-762w",
  "euvd_id": "EUVD-2026-104914",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated diagnostic information exposure in Apache Cocoon",
  "summary": "All Apache Cocoon versions allow unauthenticated access to diagnostic interfaces. An attacker who can reach an affected instance may view verbose diagnostic or profiling information and invoke cache-related functions.",
  "mitigation": "Restrict the Cocoon instance and its diagnostic interfaces to trusted users and networks. Plan to replace Apache Cocoon, as no fixed version is planned.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Cocoon",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= *"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Apache Cocoon",
      "purl": null
    }
  ],
  "cwes": [
    497
  ],
  "cvss_score": 7.5,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 89.50431611666667,
  "t0_at": "2026-10-20T10:25:54.169000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-20T10:25:54.169000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-20T10:25:54.169000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-108089"
    }
  }
}

published 2026-10-20 11:03Z
last change 2026-10-21 11:52Z

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.