Skip to content
Applications

CVE-2026-71979

8.7
High
EPSS 0.48%Patch availableAug 18, 2026

Unauthenticated remote buffer overflow in indiserver causes daemon crash (DoS)

common questions

Is CVE-2026-71979 being exploited?

Not confirmed. CVE-2026-71979 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 0.48% probability of exploitation in the next 30 days.

How severe is CVE-2026-71979?

CVE-2026-71979 is rated High with a CVSS score of 8.7. 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-71979?

Yes. A fix has been recorded for CVE-2026-71979. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-71979 affect?

CVE-2026-71979 affects INDI indiserver <= 2.2.4.2, Service listening on TCP port 7624. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-71979?

Apply patched commit/release (96bbd7f) or block TCP/7624 until patched

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
INDI indiserver <= 2.2.4.2Service listening on TCP port 7624
impact

Unauthenticated remote DoS: single TCP packet to port 7624 with oversized XML tag crashes indiserver, disrupting client/driver sessions.

action required

Immediate action required

affected versions
indilib indi
  • affected<= 2.2.4.2
vendor says fixed in96bbd7f564bbb128a129019e44eadd40dd49cff9

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free