INDI (Instrument Neutral Distributed Interface) indiserver through 2.2.4.2, fixed in commit 96bbd7f, contains a stack buffer overflow vulnerability that allows unauthenticated remote attackers to crash the daemon by sending malformed XML with mismatched tags whose names exceed 1024 bytes. Attackers can send a single TCP packet on port 7624 with mismatched XML tags to trigger an unbounded sprintf() write into a fixed 1024-byte stack buffer in MsgQueue.cpp, terminating the daemon and disrupting all active client and driver sessions.
CVE-2026-71979
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-17. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 40%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 17, 2026
Advisory Details (3)
Auto-updated Aug 17, 2026INDI indiserver 2.2.4.2 Stack Buffer Overflow via XML Tag Parsing | Advisories | VulnCheck
https://www.vulncheck.com/advisories/indi-indiserver-stack-buffer-overflow-via-xml-tag-parsingcommit 96bbd7f564bb (indilib/indi)
Fix landed in indilib/indi commit 96bbd7f564bb — awaiting tagged release
https://github.com/indilib/indi/commit/96bbd7f564bbb128a129019e44eadd40dd49cff9Unauthenticated remote stack buffer overflow in indiserver XML parser (CVE-2026-71979) · Issue #2472 · indilib/indi · GitHub
https://github.com/indilib/indi/issues/2472Vendor Advisories for CVE-2026-71979(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 21× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 03:54 UTCEG score recompute
- 2026-08-21 03:54 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 16:47 UTCGHSA enrichment
- 2026-08-20 05:24 UTCGHSA enrichment
- 2026-08-19 18:17 UTCEG score recompute
- 2026-08-19 18:17 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 05:51 UTCGHSA enrichment
- 2026-08-18 18:44 UTCEG score recompute
- 2026-08-18 18:44 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 07:37 UTCGHSA enrichment
- 2026-08-17 20:29 UTCEG score recompute
- 2026-08-17 20:29 UTCGHSA enrichment
- 2026-08-17 19:50 UTCEG score recompute
- 2026-08-17 19:50 UTCGHSA enrichment
- 2026-08-17 18:29 UTCEG score recompute
- 2026-08-17 17:45 UTCEG score recompute
- 2026-08-17 17:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-121
Frequently asked(5)
What is CVE-2026-71979?
When was CVE-2026-71979 disclosed?
Is CVE-2026-71979 actively exploited?
What is the CVSS score of CVE-2026-71979?
How do I remediate CVE-2026-71979?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-71979
Is Your Infrastructure Affected by CVE-2026-71979?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.