Eidetic-labs vulnerabilities
We track 9 vulnerabilities in Eidetic-labs products across 2 products. 9 are rated high or critical, and none are known to be exploited. The most recent was published on August 19, 2026.
Latest Eidetic-labs vulnerabilities
- 7.1 High severity
stigmem: Insufficient Verification of Data Authenticity
stigmem (pip package stigmem-node) version 0.9.0a1 contains a timestamp-handling mismatch in federation peer-token validation that can cause valid peer tokens to be incorrectly treated as expired. This affects the availability and reliability of authenticated
- 9.1 Critical severity
stigmem: Cleartext Transmission of Sensitive Information
stigmem-node contains an insecure default configuration vulnerability that allows federation traffic to traverse networks without mTLS protection when non-loopback endpoints are enabled. Operators who explicitly disabled mTLS while binding federation to non-lo
- 9.2 Critical severity
stigmem: Improper Authorization
stigmem versions before 0.9.0a2 allow unauthenticated access when authentication is disabled on non-loopback deployments. Attackers can perform read, write, and federation operations with anonymous identity when nodes are exposed outside local development envi
- 9.1 Critical severity
stigmem: Improper Certificate Validation
stigmem-node 0.9.0a1 accepts federation peer key material during peer registration without a separate administrator out-of-band fingerprint approval step. On nodes that accept federation peer registration over a network where initial registration can be interc
- 7.3 High severity
stigmem: Download of Code Without Integrity Check
stigmem-node 0.9.0a1 allows plugin signature enforcement to be disabled via a single configuration flag without a second explicit acknowledgment. If that setting is carried into an environment where plugin directories are writable by less-trusted users, unsign
- 7.5 High severity
stigmem: Improper Neutralization of Special Elements used in an SQL Command
stigmem-node 0.9.0a1 interpolates Postgres backend schema identifiers into SQL strings without defensive quoting. In the affected code path the schema value is operator-controlled, but the unsafe pattern could allow SQL injection if a schema name were derived
- 7.2 High severity
stigmem-node: Incorrect Authorization
stigmem versions before 0.9.0a12 contain a broken object level authorization vulnerability in the decay sweep endpoint that allows authenticated attackers with write credentials for one tenant to execute decay operations affecting all tenants. Attackers can su
- 8.6 High severity
stigmem-node: Authorization Bypass Through User-Controlled Key
stigmem-node before 0.9.0a12 contains a broken object level authorization (cross-tenant BOLA) vulnerability in the quarantine review endpoints. On multi-tenant deployments running the opt-in stigmem-plugin-multi-tenant, the list/count queries and _get_quaranti
- 7.2 High severity
stigmem-node: Authorization Bypass Through User-Controlled Key
stigmem-node before 0.9.0a12 contains a cross-tenant broken object level authorization (BOLA) flaw in the RTBF (right-to-be-forgotten) tombstone mechanism. issue_tombstone defaulted the tenant to "default" instead of the caller's tenant, allowing deletion reco