Stigmem
Monthly
Availability disruption in stigmem-node 0.9.0a1 (pip package by eidetic-labs) allows authenticated federation peers to have their valid peer tokens incorrectly rejected as expired due to a timestamp-handling mismatch in the federation peer-token validation logic. Impacted deployments are Stigmem nodes operating federation peer authentication paths, where authenticated federation flows may fail non-deterministically depending on which token-minting path was used. No active exploitation has been identified (no KEV listing, no public exploit), and the fix is available in 0.9.0a2.
Cleartext exposure of federation traffic in eidetic-labs stigmem-node (versions before 0.9.0a2) occurs when operators explicitly disable mTLS while binding federation endpoints to non-loopback addresses, allowing an on-path attacker to intercept and tamper with inter-node federation data. Reported by VulnCheck and tracked as an information-disclosure issue (CWE-319), it carries a CVSS 4.0 base score of 9.1 driven by high confidentiality and integrity impact. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Anonymous read/write/federation access to Stigmem nodes (versions before 0.9.0a2) is possible when operators disable authentication and bind the node to a non-loopback address, effectively bypassing authorization for the anonymous identity. Reported by VulnCheck and disclosed via GHSA-fp6w-8wpg-74g5, it affects the eidetic-labs stigmem-node package (pip). No public exploit identified at time of analysis, and no EPSS or CISA KEV signal is available; exploitation is gated on a deliberate operator misconfiguration rather than a default-config weakness.
Federation peer-registration authentication bypass in stigmem-node 0.9.0a1 lets a network-positioned attacker enroll a rogue federation peer without the required administrator out-of-band fingerprint approval, granting read access to and tampering ability over federation traffic. Reported by VulnCheck and tracked under CWE-295, it is rated CVSS 4.0 9.1 but carries meaningful exploitation prerequisites (high attack complexity plus a present attack requirement). No public exploit identified at time of analysis, and it is not listed in CISA KEV; fixed in 0.9.0a2.
Arbitrary code execution is possible in stigmem-node versions before 0.9.0a2 when a single configuration flag is used to disable plugin signature enforcement without a required second acknowledgment. Operators who carry this permissive setting from development into shared or production environments create a condition where any user with write access to the plugin directory can inject and execute unsigned, potentially malicious plugin code with the process's privileges. No public exploit code has been identified and no active exploitation is confirmed (not listed in CISA KEV); however, the resulting impact is full confidentiality, integrity, and availability compromise of the affected system.
SQL injection in stigmem-node 0.9.0a1 stems from PostgreSQL schema identifiers being interpolated into SQL strings without defensive identifier quoting. Operators using the Postgres backend in affected versions are directly impacted; the CVSS 4.0 vector (PR:H, AT:P) reflects that the current vulnerable code path requires operator-level control over schema configuration, though the unsafe pattern creates latent risk if schema names are ever derived from tenant or request input. No public exploit code exists and no CISA KEV listing has been identified; the vendor-released patch in 0.9.0a2 resolves the issue by adding identifier quoting and regression coverage.
Blind Server-Side Request Forgery in Stigmem before 0.9.0a11 allows authenticated users to redirect the application server's HTTP client toward loopback and RFC 1918 private-network destinations by supplying arbitrary values in the webhook subscription delivery_address parameter. When a matching fact-change event fires, Stigmem's backend issues an unsolicited HTTP POST to the attacker-specified internal address, enabling interaction with co-located internal services the attacker could not otherwise reach. No public exploit code and no CISA KEV listing have been identified at time of analysis; exploitation probability is currently unquantified.
Cross-tenant broken object level authorization (BOLA) in stigmem-node's decay sweep endpoint allows any authenticated write-credentialed tenant to destroy or enumerate facts belonging to all other tenants. Specifically, POST /v1/decay/sweep with ttl_seconds=0 expires every tenant's facts globally due to missing tenant_id predicates in the candidate-selection queries. This vulnerability exclusively affects multi-tenant deployments running the opt-in stigmem-plugin-multi-tenant; no public exploit or CISA KEV listing exists at time of analysis, but the integrity and availability impact against multi-tenant operators is critical.
Cross-tenant broken object level authorization (BOLA) in stigmem-node exposes quarantined facts across tenant boundaries on multi-tenant deployments. A tenant administrator holding only a standard tenant write capability can list, read, and admit or reject quarantined facts belonging to any other tenant on the same node via the /v1/quarantine endpoints - bypassing isolation enforced by the stigmem-plugin-multi-tenant plugin. No public exploit identified at time of analysis; no CISA KEV listing. Default single-tenant deployments are entirely unaffected regardless of version.
Cross-tenant broken object level authorization in stigmem-node before 0.9.0a12 allows an authenticated tenant in a multi-tenant deployment to corrupt RTBF tombstone records and trigger tenant-blind fact suppression. The root cause is twofold: the issue_tombstone function hardcoded the tenant to 'default' instead of reading it from the caller's identity, and the tombstone read-suppression path lacked a tenant_id predicate, causing deletion records to be misattributed and tombstone filtering to operate across all tenants indiscriminately. The impact is limited to deployments running the opt-in stigmem-plugin-multi-tenant; a vendor-released patch exists at 0.9.0a12, and no public exploit has been identified at time of analysis.
Availability disruption in stigmem-node 0.9.0a1 (pip package by eidetic-labs) allows authenticated federation peers to have their valid peer tokens incorrectly rejected as expired due to a timestamp-handling mismatch in the federation peer-token validation logic. Impacted deployments are Stigmem nodes operating federation peer authentication paths, where authenticated federation flows may fail non-deterministically depending on which token-minting path was used. No active exploitation has been identified (no KEV listing, no public exploit), and the fix is available in 0.9.0a2.
Cleartext exposure of federation traffic in eidetic-labs stigmem-node (versions before 0.9.0a2) occurs when operators explicitly disable mTLS while binding federation endpoints to non-loopback addresses, allowing an on-path attacker to intercept and tamper with inter-node federation data. Reported by VulnCheck and tracked as an information-disclosure issue (CWE-319), it carries a CVSS 4.0 base score of 9.1 driven by high confidentiality and integrity impact. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
Anonymous read/write/federation access to Stigmem nodes (versions before 0.9.0a2) is possible when operators disable authentication and bind the node to a non-loopback address, effectively bypassing authorization for the anonymous identity. Reported by VulnCheck and disclosed via GHSA-fp6w-8wpg-74g5, it affects the eidetic-labs stigmem-node package (pip). No public exploit identified at time of analysis, and no EPSS or CISA KEV signal is available; exploitation is gated on a deliberate operator misconfiguration rather than a default-config weakness.
Federation peer-registration authentication bypass in stigmem-node 0.9.0a1 lets a network-positioned attacker enroll a rogue federation peer without the required administrator out-of-band fingerprint approval, granting read access to and tampering ability over federation traffic. Reported by VulnCheck and tracked under CWE-295, it is rated CVSS 4.0 9.1 but carries meaningful exploitation prerequisites (high attack complexity plus a present attack requirement). No public exploit identified at time of analysis, and it is not listed in CISA KEV; fixed in 0.9.0a2.
Arbitrary code execution is possible in stigmem-node versions before 0.9.0a2 when a single configuration flag is used to disable plugin signature enforcement without a required second acknowledgment. Operators who carry this permissive setting from development into shared or production environments create a condition where any user with write access to the plugin directory can inject and execute unsigned, potentially malicious plugin code with the process's privileges. No public exploit code has been identified and no active exploitation is confirmed (not listed in CISA KEV); however, the resulting impact is full confidentiality, integrity, and availability compromise of the affected system.
SQL injection in stigmem-node 0.9.0a1 stems from PostgreSQL schema identifiers being interpolated into SQL strings without defensive identifier quoting. Operators using the Postgres backend in affected versions are directly impacted; the CVSS 4.0 vector (PR:H, AT:P) reflects that the current vulnerable code path requires operator-level control over schema configuration, though the unsafe pattern creates latent risk if schema names are ever derived from tenant or request input. No public exploit code exists and no CISA KEV listing has been identified; the vendor-released patch in 0.9.0a2 resolves the issue by adding identifier quoting and regression coverage.
Blind Server-Side Request Forgery in Stigmem before 0.9.0a11 allows authenticated users to redirect the application server's HTTP client toward loopback and RFC 1918 private-network destinations by supplying arbitrary values in the webhook subscription delivery_address parameter. When a matching fact-change event fires, Stigmem's backend issues an unsolicited HTTP POST to the attacker-specified internal address, enabling interaction with co-located internal services the attacker could not otherwise reach. No public exploit code and no CISA KEV listing have been identified at time of analysis; exploitation probability is currently unquantified.
Cross-tenant broken object level authorization (BOLA) in stigmem-node's decay sweep endpoint allows any authenticated write-credentialed tenant to destroy or enumerate facts belonging to all other tenants. Specifically, POST /v1/decay/sweep with ttl_seconds=0 expires every tenant's facts globally due to missing tenant_id predicates in the candidate-selection queries. This vulnerability exclusively affects multi-tenant deployments running the opt-in stigmem-plugin-multi-tenant; no public exploit or CISA KEV listing exists at time of analysis, but the integrity and availability impact against multi-tenant operators is critical.
Cross-tenant broken object level authorization (BOLA) in stigmem-node exposes quarantined facts across tenant boundaries on multi-tenant deployments. A tenant administrator holding only a standard tenant write capability can list, read, and admit or reject quarantined facts belonging to any other tenant on the same node via the /v1/quarantine endpoints - bypassing isolation enforced by the stigmem-plugin-multi-tenant plugin. No public exploit identified at time of analysis; no CISA KEV listing. Default single-tenant deployments are entirely unaffected regardless of version.
Cross-tenant broken object level authorization in stigmem-node before 0.9.0a12 allows an authenticated tenant in a multi-tenant deployment to corrupt RTBF tombstone records and trigger tenant-blind fact suppression. The root cause is twofold: the issue_tombstone function hardcoded the tenant to 'default' instead of reading it from the caller's identity, and the tombstone read-suppression path lacked a tenant_id predicate, causing deletion records to be misattributed and tombstone filtering to operate across all tenants indiscriminately. The impact is limited to deployments running the opt-in stigmem-plugin-multi-tenant; a vendor-released patch exists at 0.9.0a12, and no public exploit has been identified at time of analysis.