dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2026-10224

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security vulnerability has been detected in NousResearch hermes-agent up to 2026.4.30. This vulnerability affects the function _handle_webhook_request of the file gateway/platforms/feishu.py of the component Webhook Endpoint. Such manipulation leads to resource consumption. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A resource consumption vulnerability exists in the _handle_webhook_request function within gateway/platforms/feishu.py of NousResearch hermes-agent. The webhook endpoint does not properly limit or validate incoming requests, allowing remote attackers to exhaust server resources through excessive or malformed webhook requests.

MitigationImplement request rate limiting and resource bounds checking on the Feishu webhook endpoint. Consider adding request validation, timeout handling, and resource quotas to prevent consumption attacks until an official patch is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate hermes-agent installation
    Search for the hermes-agent package or source code directory in your environment. Look for directories containing 'gateway/platforms/feishu.py' or the main hermes-agent package structure.
    Affected if hermes-agent with the feishu.py module is present in your environment
  2. Verify the vulnerable file exists
    Confirm the file gateway/platforms/feishu.py exists within the hermes-agent installation. Check for the presence of the _handle_webhook_request function within this file.
    Affected if The file gateway/platforms/feishu.py exists and contains the _handle_webhook_request function
  3. Check if Feishu webhook integration is enabled
    Examine your hermes-agent configuration files, environment variables, or settings for any Feishu/Lark webhook-related configuration entries. Look for keys like 'feishu', 'webhook', or 'lark' in config files.
    Affected if Feishu webhook integration is enabled or configured in your hermes-agent setup
  4. Identify exposed webhook endpoints
    Review your web server or API gateway configuration to determine if the hermes-agent webhook endpoint is publicly accessible. Check routing configurations for paths like /webhook/feishu or similar.
    Affected if The webhook endpoint is exposed and reachable from external networks
  5. Assess resource constraint configurations
    Inspect your webhook processing setup for any rate limiting, request size limits, timeout configurations, or connection pooling settings. Check both application-level and infrastructure-level configurations.
    Affected if No rate limiting, request size limits, or resource constraints are configured for the webhook endpoint

You are affected if hermes-agent with the feishu.py module is installed, the Feishu webhook is enabled, and the endpoint is exposed without resource constraints such as rate limiting or request size limits.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement request rate limiting and resource bounds checking on the Feishu webhook endpoint. Consider adding request validation, timeout handling, and resource quotas to prevent consumption attacks until an official patch is released.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10224 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10224 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data