GHSA-gpv5-rp6w-58r8
Remote code execution vulnerability in dependency System.Drawing.Common
Blast Radius
Akka.NETAkkaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The core Akka module depended on an old System.Configuration.ConfigurationManager version 4.7.0 which transitively depends on System.Common.Drawing v4.7.0. The System.Common.Drawing v4.7.0 is affected by a remote code execution vulnerability https://github.com/advisories/GHSA-ghhp-997w-qr28.
The real-world impact of this should be low, but users should be advised to upgrade to later versions of Akka.NET.
Patches
Has the problem been patched? What versions should users upgrade to?
This issue is resolved in Akka.NET v1.4.46 and Akka.NET v1.5.0-alpha3.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
You might be able to explicitly reference System.Configuration.ConfigurationManager's NuGet package and upgrade to 6.0.1 or later without upgrading Akka.NET, but it's probably best to upgrade Akka.NET itself.
References
Are there any links users can visit to find out more?
Original issue: https://github.com/akkadotnet/akka.net/issues/6226 MSFT advisory: https://github.com/advisories/GHSA-ghhp-997w-qr28
For more information
If you have any questions or comments about this advisory:
- Open an issue in the Akka.NET repository
- Contact us on the Akka.NET Discord
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Akka | all versions | 1.4.46 |
| .NETNuGet | Akka | ≥ 1.5.0-alpha1&&< 1.5.0-alpha3 | 1.5.0-alpha3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Akka. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update Akka to 1.4.46 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gpv5-rp6w-58r8 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.
How O3 protects you
O3 pinpoints whether GHSA-gpv5-rp6w-58r8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-gpv5-rp6w-58r8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-gpv5-rp6w-58r8 in your dependencies?
O3 detects GHSA-gpv5-rp6w-58r8 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.