🛡️ GHSA-2ccx-cjjh-r2j8 — mediamtx (CVE-2026-27143)

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. Rated impact: confidentiality low, integrity low, availability low.

CVSS metrics in full

The score comes from this vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:U

• Attack vector: Network — reachable from anywhere that can route to the service.
• Attack complexity: Low — the attack works reliably, with no preparation.
• Attack requirements: None — no deployment-specific condition has to hold.
• Privileges required: None — an unauthenticated stranger can try it.
• User interaction: None — nobody has to be tricked into anything.
• Confidentiality impact: Low — limited, and the attacker does not choose what is affected.
• Integrity impact: Low — limited, and the attacker does not choose what is affected.
• Availability impact: Low — limited, and the attacker does not choose what is affected.

Weakness class

GHSA-2ccx-cjjh-r2j8 is classified as CWE-190: Integer Overflow or Wraparound. Arithmetic produces a value too large for its type and wraps around, so a later size or bounds check passes when it should not.

Affected software

GHSA-2ccx-cjjh-r2j8 is recorded against 1 package.

• github.com/bluenviron/mediamtx

Timeline and source

Published on 6 May 2026 and last revised on 20 May 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Package)
github.com (Web)

Other advisories for this package

github.com/bluenviron/mediamtx has other advisories on record. If you are patching this one, these are worth checking on the same host:

• GO-2026-4989 (published 20 May 2026)

Same weakness in other software

These advisories are the same class of weakness (CWE-190: Integer Overflow or Wraparound) in other software:

• CVE-2022-36015 (8.0 High, published 13 Jul 2026)
• CVE-2023-25667 (8.0 High, published 13 Jul 2026)
• CVE-2023-25662 (8.0 High, published 13 Jul 2026)
• CVE-2017-12864 (8.0 High, published 9 Jul 2026)
• CVE-2017-12863 (8.0 High, published 9 Jul 2026)
• CVE-2022-23575 (8.0 High, published 9 Jul 2026)
• CVE-2022-23567 (8.0 High, published 9 Jul 2026)
• CVE-2017-1000450 (8.0 High, published 2 Jul 2026)

Details

Affected Packages

References