← back to feed
CVE-2026-85250

CVE-2026-85250

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

GHSA-x9f8-58m2-93q2 ↗EUVD-2026-104191 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+3h11mkevAttacks confirmed in the real world.
Apache Software Foundation Apache Camel >= 4.0.0, < 4.18.5; >= 4.19.0, < 4.22.1
fixed in 4.18.5, 4.22.1
CWE-611 Improper Restriction of XML External Entity Reference
ETK-2026-2176Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss7.5cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
15h 29msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hpublic poc+3h11mwaiting for further signals+27h03m
0
+1h
+2h
+3h

description

Apache Camel's camel-xpath package is affected in versions 4.0.0 through 4.18.4 and 4.19.0 through 4.22.0 when XPath processing uses the InputSource document type. An unauthenticated attacker who can submit XML to that processing path may read files accessible to the Camel process or induce outbound requests through external entity resolution.

mitigation

Upgrade camel-xpath to 4.18.5 or 4.22.1, or to Apache Camel 4.23.0 where applicable. Until upgraded, do not use InputSource for XPath expressions that process untrusted XML; use the default document type and avoid parser-property overrides that relax external-entity protections.

fixed in 4.18.5, 4.22.1

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.
0.54%44th percentile
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 10:35Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+3h11m
Δ 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-19 10:35Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-85250
  2. 2026-10-20 12:36Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2176",
  "cve_id": "CVE-2026-85250",
  "display_id": "CVE-2026-85250",
  "ghsa_id": "GHSA-x9f8-58m2-93q2",
  "euvd_id": "EUVD-2026-104191",
  "status": "published",
  "anchor_state": "anchored",
  "title": "XML external entity injection in Apache Camel XPath",
  "summary": "Apache Camel's camel-xpath package is affected in versions 4.0.0 through 4.18.4 and 4.19.0 through 4.22.0 when XPath processing uses the InputSource document type. An unauthenticated attacker who can submit XML to that processing path may read files accessible to the Camel process or induce outbound requests through external entity resolution.",
  "mitigation": "Upgrade camel-xpath to 4.18.5 or 4.22.1, or to Apache Camel 4.23.0 where applicable. Until upgraded, do not use InputSource for XPath expressions that process untrusted XML; use the default document type and avoid parser-property overrides that relax external-entity protections.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Camel",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.0.0, < 4.18.5",
        ">= 4.19.0, < 4.22.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.18.5",
        "4.22.1"
      ],
      "package_name": "org.apache.camel:camel-xpath",
      "purl": null
    }
  ],
  "cwes": [
    611
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.0054,
  "epss_percentile": 0.4446,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.229323433333334,
  "t0_at": "2026-10-19T10:35:21.670000+00:00",
  "signals": {
    "public_poc": {
      "at": "2026-10-19T13:46:09+00:00",
      "days": 0.13249224537037038,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T10:35:21.670000+00:00",
      "url": "https://github.com/oscerd/CVE-2026-85250"
    },
    "trigger_signal": {
      "at": "2026-10-19T10:35:21.670000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T10:35:21.670000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-85250"
    }
  }
}

published 2026-10-20 12:35Z
last change 2026-10-21 03:59Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.