CVE-2026-114442

validatingZero is analyzing and reversing it now.

GHSA-m542-3mx3-33v9 ↗EUVD-2026-115743 ↗

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 HertzBeat 1.7.1; 1.7.2; 1.7.3; 1.8.0; 1.9.0
CWE-643 Improper Neutralization of Data within XPath Expressions ('XPath Injection')
ETK-2026-3362Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = cve.org publication
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Apache HertzBeat versions 1.7.1 through 1.9.0 inadequately validate XPath expressions used by the HTTP collector. An authenticated user permitted to create monitor templates can cause excessive CPU consumption during XML processing, reducing collector availability.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade Apache HertzBeat to version 1.9.1 or later. Restrict monitor-template creation permissions to trusted users until all instances are updated.

check
building now
exploit
not yet
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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
36m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-03 10:21Z
Δ 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

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-03 10:21Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3362",
  "cve_id": "CVE-2026-114442",
  "display_id": "CVE-2026-114442",
  "ghsa_id": "GHSA-m542-3mx3-33v9",
  "euvd_id": "EUVD-2026-115743",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Incomplete XPath validation in Apache HertzBeat",
  "summary": "Apache HertzBeat versions 1.7.1 through 1.9.0 inadequately validate XPath expressions used by the HTTP collector. An authenticated user permitted to create monitor templates can cause excessive CPU consumption during XML processing, reducing collector availability.",
  "mitigation": "Upgrade Apache HertzBeat to version 1.9.1 or later. Restrict monitor-template creation permissions to trusted users until all instances are updated.",
  "vendor": "Apache Software Foundation",
  "product": "Apache HertzBeat",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.7.1",
        "1.7.2",
        "1.7.3",
        "1.8.0",
        "1.9.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Apache HertzBeat",
      "purl": null
    }
  ],
  "cwes": [
    643
  ],
  "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": 36.20868265,
  "t0_at": "2026-11-03T10:21:06.018000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T10:21:06.018000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T10:21:06.018000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-114442"
    }
  }
}

published 2026-11-03 11:16Z
last change 2026-11-03 14: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.