CVE-2026-26975
Unauthenticated RCE via API in Music Assistant <= 2.6.3
Is CVE-2026-26975 being exploited?
Not confirmed. CVE-2026-26975 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.4% probability of exploitation in the next 30 days.
How severe is CVE-2026-26975?
CVE-2026-26975 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-26975?
Yes. A fix has been recorded for CVE-2026-26975. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-26975 affect?
CVE-2026-26975 affects Music Assistant <= 2.6.3. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-26975?
Upgrade to 2.7.0+ immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RCE via API by bypassing .m3u restriction and writing Python .pth in site-packages; container runs as root, enabling full host compromise.
Patch when possible
- affected< 2.7.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.