Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Bunkum versions 4.0.0 up to but not including 4.2.1 are affected. Cached authentication tokens in the AuthenticationService can outlive the request they were made for, and when a cached token expires and is removed from Realm, later use of it throws an exception from a detached object, which is a use-after-free. The source describes the scope as limited, with exploitation requiring specific endpoints and conditions and user interaction. Upgrade to Bunkum 4.2.1; no workaround is listed for other 4.x versions.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0054, the 46th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:24 UTC First seen by agentprime
- 31 Oct 2026, 15:24 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-jrf2-h5j6-3rrq
- OSV: GHSA-jrf2-h5j6-3rrq
- github.com/LittleBigRefresh/Bunkum/security/advisories/GHSA-jrf2-h5j6-3rrq
- nvd.nist.gov/vuln/detail/CVE-2023-45814
- github.com/LittleBigRefresh/Bunkum/commit/6e109464ed9255f558182f001f475a378405ff76
- github.com/LittleBigRefresh/Bunkum