Connext Professional: Heap-based Buffer Overflow
CVE-2026-2467 is a high-severity heap-based buffer overflow vulnerability in Connext Professional from RTI, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 7.7.0, 7.3.1.3, 6.1.* as the first without the flaw, so updating Connext Professional to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.19% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Connext Professional to 7.7.0 or 7.3.1.3 or 6.1.* or 6.0.*, whichever matches your release line, or a later version.
- Read the advisory on rti.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| RTI | Connext Professional | 7.4.0 up to, but not including, 7.7.0; 7.0.0 up to, but not including, 7.3.1.3; 6.1.0 up to, but not including, 6.1.*; 6.0.0 up to, but not including, 6.0.*; 5.3.0 up to, but not including, 5.3.*; 5.2.0 up to, but not including, 5.2.*; 5.0.0 up to, but not including, 5.1.* | 7.7.0, 7.3.1.3, 6.1.*, 6.0.*, 5.3.*, 5.2.* |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 9.2 | Critical | CNA |
| CVSS 3.1 | 8.1 | High | NVD |
Official description
Heap-based Buffer Overflow vulnerability in RTI Connext Professional (Core Libraries) allows Overflow Variables and Tags. This issue affects Connext Professional: from 7.4.0 before 7.7.0, from 7.0.0 before 7.3.1.3, from 6.1.0 before 6.1.*, from 6.0.0 before 6.0.*, from 5.3.0 before 5.3.*, from 5.2.0 before 5.2.*, from 5.0.0 before 5.1.*.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Heap-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the heap.
How developers prevent this class of flaw
- Pre-design: Use a language or compiler that performs automatic bounds checking.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- rti.com/vulnerabilities/#cve-2026-2467Mitigation
Other vulnerabilities in Connext Professional
- 7.7 High severity
- 10.0 Critical severity
- 7.3 High severity
- 9.2 Critical severity
- 8.7 High severity
- 8.3 High severity
Recent Heap-based Buffer Overflow vulnerabilities
- 8.8 High severity
- 8.8 High severity
- 7.8 High severity
- 8.8 High severity
- 8.8 High severity
- 7.8 High severity
Spotted an error? Tell us.