GHSA-r6jg-jfv6-2fjv — matrix-media-repo
MEDIUMGHSA-r6jg-jfv6-2fjv is a medium-severity (CVSS 5) Server-Side Request Forgery (SSRF) vulnerability in github.com/t2bot/matrix-media-repo. A fix is available for github.com/t2bot/matrix-media-repo — see the affected versions and patch details below.
Matrix Media Repo (MMR) allows Server-Side Request Forgery (SSRF) on redirects and federation
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-r6jg-jfv6-2fjv.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-r6jg-jfv6-2fjv plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/t2bot/matrix-media-repoReal-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
Impact
Matrix Media Repo (MMR) is vulnerable to server-side request forgery, serving content from a private network it can access, under certain conditions.
Patches
This is fixed in MMR v1.3.8.
Workarounds
Restricting which hosts MMR is allowed to contact via (local) firewall rules or a transparent proxy.
References
https://owasp.org/www-community/attacks/Server_Side_Request_Forgery https://learn.snyk.io/lesson/ssrf-server-side-request-forgery/ https://www.agwa.name/blog/post/preventing_server_side_request_forgery_in_golang
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/t2bot/matrix-media-repo | all versions | 1.3.8go get github.com/t2bot/matrix-media-repo@v1.3.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/t2bot/matrix-media-repo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/t2bot/matrix-media-repo to 1.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r6jg-jfv6-2fjv 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r6jg-jfv6-2fjv can be triaged on real exposure rather than presence alone.
Tailored to GHSA-r6jg-jfv6-2fjv. 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-r6jg-jfv6-2fjv in your dependencies?
O3 Security finds GHSA-r6jg-jfv6-2fjv across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.