Cross-Site Request Forgery in com.softwaremill.akka-http-session:core_2.12GHSA-4jf5-jggp-g56j
HIGHFix: softwaremill/akka-http-session#79GHSA-4jf5-jggp-g56j is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in com.softwaremill.akka-http-session:core_2.12. A fix is available for com.softwaremill.akka-http-session:core_2.12 — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-4jf5-jggp-g56j by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
com.softwaremill.akka-http-session:core_2.12Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
This affects the package com.softwaremill.akka-http-session:core_2.12 from 0 and before 0.6.1; all versions of package com.softwaremill.akka-http-session:core_2.11; the package com.softwaremill.akka-http-session:core_2.13 from 0 and before 0.6.1. CSRF protection can be bypassed by forging a request that contains the same value for both the X-XSRF-TOKEN header and the XSRF-TOKEN cookie value, as the check in randomTokenCsrfProtection only checks that the two values are equal and non-empty.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.softwaremill.akka-http-session:core_2.12 | ≥ 0.3.0&&< 0.6.1 | 0.6.1com.softwaremill.akka-http-session:core_2.12:0.6.1 |
Affected Products
akka-http-sessionsoftwaremillDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.softwaremill.akka-http-session:core_2.12, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.softwaremill.akka-http-session:core_2.12 to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4jf5-jggp-g56j is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-4jf5-jggp-g56j in your dependencies?
Find it across Maven, including transitive dependencies.