CVE-2024-38513 is a critical-severity (CVSS 10) CWE-384 vulnerability in github.com/gofiber/fiber. A fix is available for github.com/gofiber/fiber — see the affected versions and patch details below.
Fiber Session Middleware Token Injection Vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-38513.
EPSS Exploitation Probability
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
github.com/gofiber/fiber🐹github.com/gofiber/fiber/v2🐹github.com/gofiber/fiber/v2/middleware/sessionReal-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
A security vulnerability has been identified in the Fiber session middleware where a user can supply their own session_id value, leading to the creation of a session with that key.
Impact
The identified vulnerability is a session middleware issue in GoFiber versions 2 and above. This vulnerability allows users to supply their own session_id value, resulting in the creation of a session with that key. If a website relies on the mere presence of a session for security purposes, this can lead to significant security risks, including unauthorized access and session fixation attacks. All users utilizing GoFiber's session middleware in the affected versions are impacted.
Patches
The issue has been addressed in the latest patch. Users are strongly encouraged to upgrade to version 2.52.5 or higher to mitigate this vulnerability.
Workarounds
Users who are unable to upgrade immediately can apply the following workarounds to reduce the risk:
- Validate Session IDs: Implement additional validation to ensure session IDs are not supplied by the user and are securely generated by the server.
- Session Management: Regularly rotate session IDs and enforce strict session expiration policies.
References
For more information on session best practices:
Users are encouraged to review these references and take immediate action to secure their applications.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/gofiber/fiber | all versions | 2.52.5go get github.com/gofiber/fiber@v2.52.5 |
| 🐹Go | github.com/gofiber/fiber/v2 | all versions | 2.52.5go get github.com/gofiber/fiber/v2@v2.52.5 |
| 🐹Go | github.com/gofiber/fiber/v2/middleware/session | all versions | 2.52.5go get github.com/gofiber/fiber/v2/middleware/session@v2.52.5 |
Affected Products
fibergofiberDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gofiber/fiber, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/gofiber/fiber to 2.52.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-38513 is resolved across your whole dependency graph.
Workarounds
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
Is CVE-2024-38513 in your dependencies?
Find it across Go, including transitive dependencies.