CVE-2025-27421: Github.com/jasonlovesdoggo/abacus Goroutine Leak Vulnerability
HIGHCVE-2025-27421 is a HIGH (CVSS 7.5) goroutine leak vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting Github.com/jasonlovesdoggo/abacus libraries in the Go ecosystem. The issue involves goroutine leak in abacus sse implementation. Remediation is available by upgrading affected packages to version 0.0.0-20250302043802-898ff1204e11.
CVE-2025-27421 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
How to Fix CVE-2025-27421
To remediate this vulnerability, upgrade all affected Github.com/jasonlovesdoggo/abacus dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/jasonlovesdoggo/abacus to 0.0.0-20250302043802-898ff1204e11
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/jasonlovesdoggo/abacus
How to Check if You Are Affected
To determine whether your application is affected by CVE-2025-27421, inspect your project dependencies for Github.com/jasonlovesdoggo/abacus:
inspect dependencies for github.com/jasonlovesdoggo/abacus
Analyze the terminal output to locate any version of Github.com/jasonlovesdoggo/abacus in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.0.0-20250302043802-898ff1204e11), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In Github.com/jasonlovesdoggo/abacus, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-27421 Affected Github.com/jasonlovesdoggo/abacus Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/jasonlovesdoggo/abacus
|
Go |
< 0.0.0-20250302043802-898ff1204e11
|
0.0.0-20250302043802-898ff1204e11
|
References
Frequently Asked Questions
What is CVE-2025-27421?
Which Github.com/jasonlovesdoggo/abacus versions are affected?
What version fixes CVE-2025-27421?
Is github.com/jasonlovesdoggo/abacus affected?
What is the CVSS score of CVE-2025-27421?
What CWE is associated with CVE-2025-27421?
How can I check Go dependencies for CVE-2025-27421?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-vh64-54px-qgf8",
"modified" : "2025-03-11T17:17:30Z",
"published" : "2025-03-03T16:21:46Z",
"aliases" : [ "CVE-2025-27421" ],
"summary" : "Goroutine Leak in Abacus SSE Implementation",
"details" : "## Goroutine Leak in Abacus SSE Implementation\n\n### Summary\n\nA critical goroutine leak vulnerability has been identified in the Abacus server's Server-Sent Events (SSE) implementation. The issue occurs when clients disconnect from the `/stream` endpoint, as the server fails to properly clean up resources and terminate associated goroutines. This leads to resource exhaustion where the server continues running but eventually stops accepting new SSE connections while maintaining high memory usage. The vulnerability specifically involves improper channel cleanup in the event handling mechanism, causing goroutines to remain blocked indefinitely.\n\n### [POC](https://github.com/JasonLovesDoggo/abacus/blob/main/docs/bugs/GHSA-vh64-54px-qgf8/test.py)\n\n### Impact\n\nThis vulnerability affects all versions of Abacus prior to v1.4.0. The issue causes:\n\n- Permanent unresponsiveness of the `/stream` endpoint after prolonged use\n- Memory growth that stabilizes at a high level but prevents proper functionality\n- Selective denial of service affecting only SSE connections while other endpoints remain functional\n- Accumulated orphaned goroutines that cannot be garbage collected\n- High resource consumption under sustained client connection/disconnection patterns\n\nSystems running Abacus in production with client applications that frequently establish and terminate SSE connections are most vulnerable. The issue becomes particularly apparent in high-traffic environments or during connection stress testing.\n\n### Patches\n\nThe vulnerability has been patched in Abacus v1.4.0. The fix includes:\n\n1. Implementing buffered channels to prevent blocking operations during cleanup\n2. Adding proper mutex-protected cleanup logic to ensure resources are released exactly once\n3. Implementing timeout protection for channel operations to prevent deadlocks\n4. Ensuring consistent cleanup when connections terminate unexpectedly\n5. Adding improved monitoring for client disconnections using request context\n6. Restructuring the event broadcasting system to safely handle client removal\n\nUsers should upgrade to v1.4.0 or later versions as soon as possible.\n\n### Workarounds\n\nIf upgrading is not immediately possible, the following workarounds can help mitigate the issue:\n\n1. **Limit maximum connections**: Configure your reverse proxy to limit the maximum number of concurrent connections to the `/stream` endpoints.\n\n2. **Implement request timeouts**: Configure your infrastructure to terminate long-lived SSE connections after a reasonable period.\n\n3. **Restart regularly**: Schedule regular restarts of the Abacus service to reclaim resources.\n\n4. **Monitor memory usage**: Set up alerts for abnormal memory growth patterns.\n\n5. **Separate instance for SSE**: Run a dedicated Abacus instance solely for handling SSE connections, allowing it to be restarted without affecting the main API functionality.\n\n### References\n\n- [Go Concurrency Patterns: Context](https://blog.golang.org/context)\n- [CWE-772: Missing Release of Resource after Effective Lifetime](https://cwe.mitre.org/data/definitions/772.html)\n- [OWASP Top 10: Resource Exhaustion](https://owasp.org/www-project-top-ten/2017/A5_2017-Broken_Access_Control)\n- [Resource Management in Go](https://go.dev/blog/defer-panic-and-recover)\n\n### For More Information\n\nPlease contact the Abacus security team at abacus@jsn.cam for additional information or to report further security issues.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/jasonlovesdoggo/abacus"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.0.0-20250302043802-898ff1204e11"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/JasonLovesDoggo/abacus/security/advisories/GHSA-vh64-54px-qgf8"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-27421"
}, {
"type" : "WEB",
"url" : "https://github.com/JasonLovesDoggo/abacus/commit/78fdb9b48b7f6d08ed0cd41077509c0a97071552"
}, {
"type" : "WEB",
"url" : "https://github.com/JasonLovesDoggo/abacus/commit/898ff1204e11317cc161240b660e63eed5a72b33"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/JasonLovesDoggo/abacus"
}, {
"type" : "WEB",
"url" : "https://pkg.go.dev/vuln/GO-2025-3498"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-400", "CWE-772" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2025-03-03T16:21:46Z",
"nvd_published_at" : "2025-03-03T17:15:15Z"
}
}