NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

Insufficient Session Expiration in NakamaGHSA-xv59-gc3r-rf92

HIGHFix: heroiclabs/nakama@ce8d392

GHSA-xv59-gc3r-rf92 is a high-severity (CVSS 7.5) CWE-613 vulnerability in github.com/heroiclabs/nakama. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2022-2306
Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
1 known
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk
0.00%0.46%0.92%1.38%0.2%0.9%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹github.com/heroiclabs/nakama

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Old session tokens can be used to authenticate to the application and send authenticated requests.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/heroiclabs/nakamaall versionsNo fix

Affected Products

1 product · 1 configurations
Application
nakamaheroiclabs
< 3.13.0
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Old session tokens can be used to authenticate to the application and se…

huntr.devNVDJul 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/heroiclabs/nakama, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    The records we use list no patched version of github.com/heroiclabs/nakama for GHSA-xv59-gc3r-rf92. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Old session tokens can be used to authenticate to the application and send authenticated requests.
O3 Security · Impact-Aware SCA

Is GHSA-xv59-gc3r-rf92 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Insufficient Session Expiration in Nakama (High 7.5)