GHSA-wmg4-8cp2-hpg9
HIGHGHSA-wmg4-8cp2-hpg9 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in matrix-sydent. O3 Security confirms whether GHSA-wmg4-8cp2-hpg9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Sydent vulnerable to denial of service attack via memory exhaustion
Blast Radius
matrix-sydentReal-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
Sydent does not limit the size of requests it receives from HTTP clients. A malicious user could send an HTTP request with a very large body, leading to disk space exhaustion and denial of service.
Sydent also does not limit response size for requests it makes to remote Matrix homeservers. A malicious homeserver could return a very large response, again leading to memory exhaustion and denial of service.
This affects any server which accepts registration requests from untrusted clients.
Patches
Patched by 89071a1, 0523511, f56eee3.
Workarounds
Request sizes can be limited in an HTTP reverse-proxy.
There are no known workarounds for the problem with overlarge responses.
For more information
If you have any questions or comments about this advisory, email us at [email protected].
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | matrix-sydent | all versions | 2.3.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for matrix-sydent. 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-sydent to 2.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wmg4-8cp2-hpg9 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-wmg4-8cp2-hpg9 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-wmg4-8cp2-hpg9. 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-wmg4-8cp2-hpg9 in your dependencies?
O3 detects GHSA-wmg4-8cp2-hpg9 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.