CVE-2026-114463

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

GHSA-4h98-2jhp-qgm2 ↗EUVD-2026-107306 ↗

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.
Nous Research Hermes Agent <= 2026.8.19
ETK-2026-2339Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 48msince last run
26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h58m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Hermes Agent's webhook gateway can resolve a colon-containing route name to a different route when determining toolset permissions. An attacker holding the target webhook HMAC may obtain toolsets assigned to a higher-privileged route.

mitigation

Disallow colons in webhook route names and review existing routes for ambiguous prefix relationships. Restrict access to webhook HMAC secrets and rotate them where exposure is suspected; no fixed version is recorded.

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
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 15:01Z
Δ 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 15:01Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2339",
  "cve_id": "CVE-2026-114463",
  "display_id": "CVE-2026-114463",
  "ghsa_id": "GHSA-4h98-2jhp-qgm2",
  "euvd_id": "EUVD-2026-107306",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in Hermes Agent webhook gateway",
  "summary": "Hermes Agent's webhook gateway can resolve a colon-containing route name to a different route when determining toolset permissions. An attacker holding the target webhook HMAC may obtain toolsets assigned to a higher-privileged route.",
  "mitigation": "Disallow colons in webhook route names and review existing routes for ambiguous prefix relationships. Restrict access to webhook HMAC secrets and rotate them where exposure is suspected; no fixed version is recorded.",
  "vendor": "Nous Research",
  "product": "Hermes Agent",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2026.8.19"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Hermes Agent",
      "purl": null
    }
  ],
  "cwes": null,
  "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": 25.529341266666666,
  "t0_at": "2026-10-21T15:01:02.634000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-21T15:01:02.634000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T15:01:02.634000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-114463"
    }
  }
}

published 2026-10-21 17:33Z
last change 2026-10-21 19:22Z

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.