CVE-2026-7396
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 · uneditedA vulnerability was identified in NousResearch hermes-agent 0.8.0. Affected by this issue is some unknown functionality of the file gateway/platforms/wecom.py of the component WeChat Work Platform Adapter. The manipulation leads to path traversal. It is possible to initiate the attack remotely. The exploit is publicly available and might be used.
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 confidenceA path traversal vulnerability exists in the WeChat Work Platform Adapter (wecom.py) of NousResearch hermes-agent 0.8.0. The file gateway functionality fails to properly sanitize file path inputs, allowing attackers to manipulate file paths using '..' or absolute path sequences to access files outside the intended directory.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify hermes-agent versionRun 'pip show hermes-agent' or check the package version in your environment to confirm version 0.8.0 is installedAffected if Version is exactly 0.8.0 or falls within the 0.8.x range prior to any patched release
-
Locate wecom.py adapter fileFind the wechat work adapter file (wecom.py) in the hermes-agent installation directory, typically under agents/adapters/ or similar pathAffected if The wecom.py file exists in the installation
-
Verify file gateway feature is enabledCheck configuration files or runtime settings for WeChat Work integration to see if the file transfer/gateway functionality is actively configuredAffected if File gateway or file transfer features are enabled for WeChat Work integration
-
Inspect file path handling in wecom.pyReview the wecom.py source code for file operations, specifically looking for functions that accept file path parameters without proper sanitization checksAffected if Code contains file operations using user-supplied paths without validation for '..' or absolute path sequences
You are affected if hermes-agent version 0.8.0 is installed with WeChat Work adapter enabled and the file gateway functionality is in use, as the path traversal flaw requires the vulnerable file handling code to be reachable through user-controlled file path inputs.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict input validation and path sanitization for all file path parameters in the WeChat Work adapter, ensuring paths are constrained to allowed directories and rejecting any path containing traversal sequences.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7396 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7396 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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