CVE-2026-11330 Overview
CVE-2026-11330 is a weak hash algorithm vulnerability [CWE-327] in the thedotmack/claude-mem project, affecting versions up to 11.0.1. The flaw resides in the computeObservationContentHash function within src/services/sqlite/observations/store.ts, part of the Observation Content Hash Handler component. The function relies on a cryptographically weak hash to derive observation content identifiers, which can lead to collisions or predictable outputs in the local SQLite store. Exploitation requires local access, elevated complexity, and yields limited integrity and availability impact. The maintainer addressed the issue in version 12.0.0 via commit f32fda8b35e9fe9329f87da65c31149362a03f97.
Critical Impact
A local attacker with low privileges could exploit hash collisions in the observation store to tamper with stored records, though exploitation difficulty is high and confidentiality is unaffected.
Affected Products
- thedotmack/claude-mem versions up to and including 11.0.1
- Component: Observation Content Hash Handler (src/services/sqlite/observations/store.ts)
- Function: computeObservationContentHash
Discovery Timeline
- 2026-06-05 - CVE-2026-11330 published to NVD
- 2026-06-05 - Last updated in NVD database
Technical Details for CVE-2026-11330
Vulnerability Analysis
The vulnerability is categorized under [CWE-327] (Use of a Broken or Risky Cryptographic Algorithm). The computeObservationContentHash function generates content hashes used to uniquely identify observation records persisted in a local SQLite database. Because the function uses a cryptographically weak hashing primitive, an attacker capable of crafting input data can produce collisions or otherwise predictable outputs. This undermines the integrity guarantees the hash is meant to provide when deduplicating or referencing stored observations.
The attack surface is constrained to local interaction with the claude-mem data store. The exploitability is rated as difficult, and the impact is limited to partial integrity and availability degradation. Confidentiality is not affected because the hash output itself does not disclose sensitive content.
Root Cause
The root cause is the selection of a cryptographically weak hash algorithm to derive content identifiers in src/services/sqlite/observations/store.ts. Weak hashes such as MD5 or SHA-1 do not provide adequate collision resistance for content-addressable storage scenarios. The patch in commit f32fda8b35e9fe9329f87da65c31149362a03f97 replaces the weak primitive with a stronger algorithm suitable for content hashing.
Attack Vector
The attack vector is local. An authenticated user with access to the claude-mem runtime environment must supply specially crafted observation content that triggers a hash collision against an existing record. A successful collision could allow the attacker to overwrite, shadow, or corrupt observation entries referenced by their computed hash. The high attack complexity reflects the cryptographic effort required to engineer a usable collision against the targeted observation store.
No public proof-of-concept exploit code has been published. For technical context, refer to the GitHub Commit Details and the GitHub Pull Request.
Detection Methods for CVE-2026-11330
Indicators of Compromise
- Unexpected modification timestamps on the local claude-mem SQLite database file outside normal application activity.
- Duplicate or overwritten observation records sharing identical content hashes but distinct payloads.
- Presence of claude-mem package versions at or below 11.0.1 in project manifests or node_modules directories.
Detection Strategies
- Inventory installed versions of thedotmack/claude-mem across developer endpoints and CI runners and flag versions prior to 12.0.0.
- Audit observation records for integrity by recomputing strong hashes over stored content and comparing against persisted identifiers.
- Monitor source code repositories for imports of claude-mem and confirm that lockfiles reference the patched release.
Monitoring Recommendations
- Track file integrity on the local SQLite database backing the observation store for unauthorized writes.
- Log invocations of computeObservationContentHash during development and review for anomalous collision patterns.
- Include this CVE in dependency scanning baselines using tools that consume NVD or VulDB CVE-2026-11330 feeds.
How to Mitigate CVE-2026-11330
Immediate Actions Required
- Upgrade thedotmack/claude-mem to version 12.0.0 or later in all projects and developer environments.
- Update lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock) and rebuild dependency trees to ensure the patched version is resolved.
- Restrict local access to systems running claude-mem to trusted users only until upgrades are verified.
Patch Information
The vulnerability is resolved in claude-mem version 12.0.0. The fix is delivered in commit f32fda8b35e9fe9329f87da65c31149362a03f97, merged via pull request 1494. Release artifacts are available at the GitHub Release v12.0.0. Review the GitHub Project Repository for downstream guidance.
Workarounds
- If immediate upgrade is not feasible, limit shell access to hosts where claude-mem is installed to prevent local attackers from supplying crafted observation content.
- Periodically validate the integrity of the observation SQLite store and discard entries with anomalous hash collisions.
- Avoid sharing the claude-mem data directory across untrusted user accounts on the same host.
# Upgrade claude-mem to the patched release
npm install claude-mem@12.0.0
# Verify the installed version
npm ls claude-mem
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

