Summary
MediaMTX affected by CVE-2026-27143 due to vulnerable dependency
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
Impact
An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value. Typical impact: incorrect size calculations leading to heap overflows or logic errors.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-2CCX-CJJH-R2J8? GHSA-2CCX-CJJH-R2J8 is a low-severity integer overflow or wraparound vulnerability in github.com/bluenviron/mediamtx (go), affecting versions >= 1.15.0, < 1.18.0. It is fixed in 1.18.0. An arithmetic operation produces a value that exceeds the integer type's maximum, causing it to wrap to an unexpected small value.
- Which versions of github.com/bluenviron/mediamtx are affected by GHSA-2CCX-CJJH-R2J8? github.com/bluenviron/mediamtx (go) versions >= 1.15.0, < 1.18.0 is affected.
- Is there a fix for GHSA-2CCX-CJJH-R2J8? Yes. GHSA-2CCX-CJJH-R2J8 is fixed in 1.18.0. Upgrade to this version or later.
- Is GHSA-2CCX-CJJH-R2J8 exploitable, and should I be worried? Whether GHSA-2CCX-CJJH-R2J8 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-2CCX-CJJH-R2J8 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-2CCX-CJJH-R2J8? Upgrade
github.com/bluenviron/mediamtxto 1.18.0 or later.