How severe is GHSA-2ccx-cjjh-r2j8?

No CVSS score has been assigned to GHSA-2ccx-cjjh-r2j8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2ccx-cjjh-r2j8?

GHSA-2ccx-cjjh-r2j8 affects the following packages: github.com/bluenviron/mediamtx (Go). Ecosystems affected: Go.

How do I fix GHSA-2ccx-cjjh-r2j8?

Update github.com/bluenviron/mediamtx to 1.18.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2ccx-cjjh-r2j8 is resolved across your whole dependency graph.

How do I detect GHSA-2ccx-cjjh-r2j8 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bluenviron/mediamtx, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2ccx-cjjh-r2j8 if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-2ccx-cjjh-r2j8?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2ccx-cjjh-r2j8 can be triaged on real exposure rather than presence alone.

Is GHSA-2ccx-cjjh-r2j8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2ccx-cjjh-r2j8 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.

When was GHSA-2ccx-cjjh-r2j8 published, and has it been updated?

GHSA-2ccx-cjjh-r2j8 was published on May 6, 2026 and was last updated on May 20, 2026. 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

GHSA-2ccx-cjjh-r2j8 — mediamtx

GHSA-2ccx-cjjh-r2j8 is a security vulnerability in github.com/bluenviron/mediamtx. A fix is available for github.com/bluenviron/mediamtx — see the affected versions and patch details below.

MediaMTX affected by CVE-2026-27143 due to vulnerable dependency

Also known asGO-2026-4989

Published

May 6, 2026

Updated

May 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 20, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/bluenviron/mediamtx

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

Summary

Release 1.17.1 seems affected by CVE-2026-27143. golang 1.25.9 Seems to solve the issue. Is there any new release planned?

Details

See https://nvd.nist.gov/vuln/detail/CVE-2026-27143.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/bluenviron/mediamtx`	≥ 1.15.0&&< 1.18.0	1.18.0`go get github.com/bluenviron/mediamtx@v1.18.0`

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/bluenviron/mediamtx, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/bluenviron/mediamtx to 1.18.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2ccx-cjjh-r2j8 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-2ccx-cjjh-r2j8 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-2ccx-cjjh-r2j8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Release 1.17.1 seems affected by CVE-2026-27143. golang 1.25.9 Seems to solve the issue. Is there any new release planned? ### Details See https://nvd.nist.gov/vuln/detail/CVE-2026-27143.

O3 Security · Impact-Aware SCA

Is GHSA-2ccx-cjjh-r2j8 in your dependencies?

O3 Security finds GHSA-2ccx-cjjh-r2j8 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works