Persistent memory writes via post-filter tool reinjection
Published Aug 6, 2026 · Updated Aug 6, 2026
Improper access control in Hermes Agent 0.16.0 and earlier allows remote authenticated users to write persistent memory through provider tools. After model_tools.py removes the disabled memory toolset, agent_init.py appends provider schemas such as fact_store to agent.tools and valid_tool_names without rechecking disabled_toolsets. A configured memory provider and a session that disables memory are required; model influence then suffices to persist or mutate long-term memory.
Summary
What happened
Improper access control in Hermes Agent 0.16.0 and earlier allows remote authenticated users to write persistent memory through provider tools. After model_tools.py removes the disabled memory toolset, agent_init.py appends provider schemas such as fact_store to agent.tools and valid_tool_names without rechecking disabled_toolsets. A configured memory provider and a session that disables memory are required; model influence then suffices to persist or mutate long-term memory.
The record
- CVE
- CVE-2026-18993
- Published
- Aug 6, 2026
- Updated
- Aug 6, 2026
- Vendor
- Nous Research
- Product
- Hermes Agent
- Classifications
- CWE-266, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 6, 2026CVE publishedPublication date reported by the CVE source.
- Aug 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.1
- Affected versionversion=0.10
- Affected versionversion=0.11
- Affected versionversion=0.12
- Affected versionversion=0.13
- Affected versionversion=0.14
- Affected versionversion=0.15
- Affected versionversion=0.16.0
- Affected versionversion=0.2
- Affected versionversion=0.3
- Affected versionversion=0.4
- Affected versionversion=0.5
- Affected versionversion=0.6
- Affected versionversion=0.7
- Affected versionversion=0.8
- Affected versionversion=0.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- verification_test.py integration PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo