98 matches found
PT-2026-78421
Name of the Vulnerable Software and Affected Versions stigmem-node version 0.9.0a1 Description The software interpolates Postgres backend schema identifiers into SQL strings without defensive quoting. While the schema value in the affected code path is operator-controlled, this pattern could allo...
PT-2026-78420
Name of the Vulnerable Software and Affected Versions Stigmem versions prior to 0.9.0a11 Description Authenticated users can perform blind Server-Side Request Forgery SSRF attacks by specifying internal loopback or private network destinations in the delivery address parameter during the creation...
CVE-2026-76240: 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 from tenant, request, or user input...
PT-2026-78426
Name of the Vulnerable Software and Affected Versions stigmem pip package stigmem-node version 0.9.0a1 Description A timestamp-handling mismatch exists in federation peer-token validation. This issue can cause valid peer tokens to be incorrectly treated as expired, impacting the availability and...
CVE-2026-76245: 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 federation flows on nodes using...
CVE-2026-76244: 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-loopback addresses expose federation...
PT-2026-78417
Name of the Vulnerable Software and Affected Versions stigmem-node versions prior to 0.9.0a12 Description A broken object level authorization BOLA flaw exists in the right-to-be-forgotten RTBF tombstone mechanism. The issue tombstone function defaulted the tenant to "default" instead of the...
PT-2026-78423
Name of the Vulnerable Software and Affected Versions stigmem-node version 0.9.0a1 Description stigmem-node accepts federation peer key material during peer registration without requiring a separate administrator out-of-band fingerprint approval step. On nodes that accept federation peer...
CVE-2026-76242: 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 intercepted or misdirected, an attacker can...
CVE-2026-76241: 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, unsigned potentially malicious plugin code...
CVE-2026-76239: Server-Side Request Forgery (SSRF)
Stigmem before 0.9.0a11 fails to validate the deliveryaddress parameter when creating webhook subscriptions, allowing authenticated users to specify internal loopback and private network destinations. Attackers can trigger matching fact-change events to cause the Stigmem server to issue server-si...
CVE-2026-76237: 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 getquarantinedfact in routes/quarantine.py lacked a...
CVE-2026-76238: 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 submit POST requests to the decay sweep...
CVE-2026-76243: 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 environments...
CVE-2026-76236: 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. issuetombstone defaulted the tenant to "default" instead of the caller's tenant, allowing deletion records to be written to the wrong tenant, and...
PT-2026-78425
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-loopback addresses expose federation...
Incorrect Authorization
Overview stigmem-node is a Stigmem reference node — single-host production implementation Affected versions of this package are vulnerable to Incorrect Authorization in the rundecaysweep process. An attacker can access or modify data belonging to other tenants by initiating a decay sweep with a...
stigmem-node: decay sweep expires and counts facts across all tenants (cross-tenant BOLA)
Summary On a multi-tenant stigmem node, a caller holding a write credential for one tenant can run a decay sweep that acts on every tenant's facts. The candidate-selection queries in lifecycle/decay.py selectttlcandidates, selectconfidencecandidates carried no tenantid predicate, and the caller's...
GHSA-6GQW-JQV7-V88M stigmem-node: decay sweep expires and counts facts across all tenants (cross-tenant BOLA)
Summary On a multi-tenant stigmem node, a caller holding a write credential for one tenant can run a decay sweep that acts on every tenant's facts. The candidate-selection queries in lifecycle/decay.py selectttlcandidates, selectconfidencecandidates carried no tenantid predicate, and the caller's...
Incorrect Authorization
Overview stigmem-node is a Stigmem reference node — single-host production implementation Affected versions of this package are vulnerable to Incorrect Authorization in the routes/quarantine.py process. An attacker can access and modify other tenants' quarantined data by sending requests to the...