How severe is GHSA-8vmr-h7h5-cqhg?

GHSA-8vmr-h7h5-cqhg has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-8vmr-h7h5-cqhg?

GHSA-8vmr-h7h5-cqhg affects the following packages: github.com/t2bot/matrix-media-repo (Go). Ecosystems affected: Go.

How do I fix GHSA-8vmr-h7h5-cqhg?

Update github.com/t2bot/matrix-media-repo to 1.3.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8vmr-h7h5-cqhg is resolved across your whole dependency graph.

How do I detect GHSA-8vmr-h7h5-cqhg in my Go dependencies?

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.

How do I mitigate GHSA-8vmr-h7h5-cqhg if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-8vmr-h7h5-cqhg actively exploited in the wild?

No public exploit code has been indexed for GHSA-8vmr-h7h5-cqhg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-8vmr-h7h5-cqhg?

GHSA-8vmr-h7h5-cqhg has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-8vmr-h7h5-cqhg?

GHSA-8vmr-h7h5-cqhg is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-8vmr-h7h5-cqhg published, and has it been updated?

GHSA-8vmr-h7h5-cqhg was published on January 16, 2025 and was last updated on August 20, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

MEDIUM severity

matrix-media-repo (MMR) allows unauthenticated writes to the media repository, which may allow planting of problematic contentGHSA-8vmr-h7h5-cqhg

MEDIUMFix: matrix-org/matrix-spec-proposals#3916

GHSA-8vmr-h7h5-cqhg is a medium-severity (CVSS 5.3) Improper Authentication 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.

Also known asCVE-2024-36402GO-2025-3397

Published

Jan 16, 2025

Updated

Aug 20, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-8vmr-h7h5-cqhg.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹github.com/t2bot/matrix-media-repo

Real-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

MMR before version 1.3.5 allows, by design, unauthenticated remote participants to trigger a download and caching of remote media from a remote homeserver to the local media repository. Such content then also becomes available for download from the local homeserver in an unauthenticated way. The implication is that unauthenticated remote adversaries can use this functionality to plant problematic content into the media repository.

Patches

MMR 1.3.5 introduces a partial mitigation in the form of new endpoints which require authentication for media downloads. The unauthenticated endpoints will be frozen in a future release, closing the attack vector.

Workarounds

Though extremely limited, server operators can use more strict rate limits based on IP address.

References

https://github.com/matrix-org/matrix-spec-proposals/pull/3916

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/t2bot/matrix-media-repo`	all versions	1.3.5`go get github.com/t2bot/matrix-media-repo@v1.3.5`

Affected Products

1 product · 1 configurations

Application

matrix-media-repot2bot

< 1.3.5

range

Detection & mitigation playbook

Open-source dependency

Detect
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.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8vmr-h7h5-cqhg is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact MMR before version 1.3.5 allows, by design, unauthenticated remote participants to trigger a download and caching of remote media from a remote homeserver to the local media repository. Such content then also becomes available for download from the local homeserver in an unauthenticated way. The implication is that unauthenticated remote adversaries can use this functionality to plant problematic content into the media repository. ### Patches MMR 1.3.5 introduces a partial mitigation in the form of new endpoints which require authentication for media downloads. The unauthenticate