GHSA-5wrh-4jwv-5w78 is a medium-severity (CVSS 6.3) Open Redirect vulnerability in matrix-synapse. O3 Security confirms whether GHSA-5wrh-4jwv-5w78 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Open redirect via transitional IPv6 addresses on dual-stack networks
Real-World Exposure
matrix-synapseReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Requests to user provided domains were not restricted to external IP addresses when transitional IPv6 addresses were used. Outbound requests to federation, identity servers, when calculating the key validity for third-party invite events, sending push notifications, and generating URL previews are affected. This could cause Synapse to make requests to internal infrastructure on dual-stack networks.
Patches
This issue is fixed by #9240.
Workarounds
Outbound requests to the following address ranges can be blocked by a firewall, if unused for internal communication between systems:
::ffff/80::0000/80(note that this IP range is considered deprecated by the IETF)2002::/16(note that this IP range is considered deprecated by the IETF)
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | matrix-synapse | all versions | 1.28.0rc1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for matrix-synapse. 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 matrix-synapse to 1.28.0rc1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5wrh-4jwv-5w78 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-5wrh-4jwv-5w78 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-5wrh-4jwv-5w78. 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-5wrh-4jwv-5w78 in your dependencies?
O3 detects GHSA-5wrh-4jwv-5w78 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.