Lucene search
+L

9 matches found

Cvelist
Cvelist
•added 2026/08/07 10:36 p.m.•73 views

CVE-2026-52879 Klever-Go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoS

Klever-Go is the Go implementation of the Klever blockchain protocol. In versions 1.7.14 through 1.7.17, the direct-message ingress handler spawns a new goroutine for every incoming direct message before the processor-level antiflood layer makes any admission decision, with no semaphore, throttle...

7.5CVSS0.00488EPSS
SaveExploits0References2
Vulnrichment
Vulnrichment
•added 2026/08/07 10:36 p.m.•14 views

CVE-2026-52879 Klever-Go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoS

Klever-Go is the Go implementation of the Klever blockchain protocol. In versions 1.7.14 through 1.7.17, the direct-message ingress handler spawns a new goroutine for every incoming direct message before the processor-level antiflood layer makes any admission decision, with no semaphore, throttle...

7.5CVSS8.2AI score0.00488EPSS
SaveExploits0References2
osv_cve
osv_cve
•added 2026/08/07 10:36 p.m.•23 views

CVE-2026-52879 Klever-Go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoS

Klever-Go is the Go implementation of the Klever blockchain protocol. In versions 1.7.14 through 1.7.17, the direct-message ingress handler spawns a new goroutine for every incoming direct message before the processor-level antiflood layer makes any admission decision, with no semaphore, throttle...

7.5CVSS5.9AI score
SaveExploits0References4
CVE
CVE
•added 2026/08/07 10:36 p.m.•98 views

CVE-2026-52879

Summary: CVE-2026-52879 affects Klever-Go (Go implementation of Klever) where the direct-message ingress path spawns a new goroutine for every incoming direct message before the antiflood layer decides admission. This creates unbounded goroutine growth per peer, increasing stack allocations and G...

7.5CVSS8.2AI score0.00488EPSS
SaveExploits0References2
Rapid7 Vulnerability Database (full)
Rapid7 Vulnerability Database (full)
•added 2026/08/07 12:00 a.m.•6 views

CVE-2026-52879: Uncontrolled Resource Consumption

Klever-Go is the Go implementation of the Klever blockchain protocol. In versions 1.7.14 through 1.7.17, the direct-message ingress handler spawns a new goroutine for every incoming direct message before the processor-level antiflood layer makes any admission decision, with no semaphore, throttle...

7.5CVSS8.3AI score0.00488EPSS
SaveExploits0References3
osv_go
osv_go
•added 2026/06/25 10:34 p.m.•35 views

GO-2026-5424 klever-go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoS in github.com/klever-io/klever-go

klever-go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoS in github.com/klever-io/klever-go...

7.5CVSS8.4AI score0.00488EPSS
SaveExploits0References2
Github Security Blog
Github Security Blog
•added 2026/03/21 3:31 a.m.•25 views

Duplicate Advisory: OpenClaw's Slack reaction/pin sender-policy consistency issue in non-message ingress

Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-rm2p-j3r7-4x4j. This link is maintained to preserve external references. Original Description OpenClaw versions prior to 2026.2.25 fail to consistently apply sender-policy checks to reaction and pin non-message...

5.3CVSS5.6AI score0.00208EPSS
SaveExploits0References6Affected Software1
Github Security Blog
Github Security Blog
•added 2026/03/03 7:50 p.m.•24 views

OpenClaw's Slack reaction/pin sender-policy consistency issue in non-message ingress

Summary OpenClaw Slack monitor handled reaction and pin non-message events before applying sender-policy checks consistently. In affected versions, these events could be added to system-event context even when sender policy would not normally allow them. Affected Packages / Versions - Package: np...

5.3CVSS5.8AI score0.00208EPSS
SaveExploits0References6Affected Software1
Positive Technologies
Positive Technologies
•added 2026/03/03 12:00 a.m.•10 views

PT-2026-25407

Summary In [email protected], BlueBubbles group authorization could incorrectly treat DM pairing-store identities as group allowlist identities when dmPolicy=pairing and groupPolicy=allowlist. A sender that was only DM-paired not explicitly present in groupAllowFrom could pass group sender check...

4.3CVSS6AI score0.00307EPSS
SaveExploits0References7
Rows per page
Query Builder