Skip to main content
CVE Vulnerability Database

CVE-2026-2674: RTI Connext Buffer Overflow Vulnerability

CVE-2026-2674 is a buffer overflow vulnerability in RTI Connext Professional affecting Queueing Service, Core Libraries, and Persistence Service. This post covers technical details, affected versions, and mitigation.

Published:

CVE-2026-2674 Overview

CVE-2026-2674 is an out-of-bounds write vulnerability affecting multiple components of RTI Connext Professional, including the Queueing Service, Core Libraries, and Persistence Service. The flaw permits buffer overflow conditions when affected components process specific input, allowing a local authenticated attacker to influence integrity and availability. The vulnerability is tracked under CWE-787 and requires local access with low privileges. RTI has published details in their RTI Vulnerability Overview.

Critical Impact

A local, authenticated attacker can trigger out-of-bounds writes in three Connext Professional components, leading to memory corruption that impacts integrity and availability of distributed real-time messaging workloads.

Affected Products

  • RTI Connext Professional 7.4.0 before 7.7.0
  • RTI Connext Professional 7.0.0 before 7.3.1.3
  • RTI Connext Professional 6.1.0 through 6.1.* (Queueing Service, Core Libraries, Persistence Service)

Discovery Timeline

  • 2026-06-17 - CVE-2026-2674 published to NVD
  • 2026-06-17 - Last updated in NVD database

Technical Details for CVE-2026-2674

Vulnerability Analysis

The vulnerability is an out-of-bounds write condition present in three distinct Connext Professional components: the Queueing Service, the Core Libraries, and the Persistence Service. Each instance allows attacker-influenced data to be written beyond the bounds of an allocated buffer. The result is buffer overflow behavior that can corrupt adjacent memory structures used by the Data Distribution Service (DDS) runtime.

Connext Professional is widely deployed in industrial, defense, and autonomous systems for real-time data exchange. Memory corruption in these components affects local integrity and availability but does not expose confidential data, according to the published vector. Exploitation requires the attacker to already possess local access with low privileges on the host running the affected service.

Root Cause

The root cause is improper validation of buffer boundaries during write operations within the affected components. The defect maps to [CWE-787: Out-of-bounds Write]. Insufficient bounds checks permit writes past the end of fixed-size buffers when parsing or processing data inside the Queueing Service, Core Libraries, and Persistence Service code paths.

Attack Vector

The attack vector is local. An attacker with low-privileged access to a system running an affected Connext Professional component sends crafted input that traverses the vulnerable write path. Successful exploitation corrupts memory and can interrupt service operation or modify in-memory state used by the DDS middleware. No user interaction is required.

No public proof-of-concept or active exploitation has been reported. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Refer to the RTI Vulnerability Overview for vendor-provided technical context.

Detection Methods for CVE-2026-2674

Indicators of Compromise

  • Unexpected crashes, restarts, or signal terminations of rtiqueuingservice, rtipersistenceservice, or processes linked against Connext Core Libraries.
  • Anomalous memory access violations or core dumps generated by Connext Professional processes on hosts running affected versions.
  • Local users invoking Connext command-line tools or APIs outside of normal operational patterns.

Detection Strategies

  • Inventory Connext Professional installations and flag any instance matching the affected version ranges 6.1.x, 7.0.0–7.3.1.2, or 7.4.0–7.6.x.
  • Monitor process exit codes and crash telemetry from DDS service binaries for repeated abnormal terminations.
  • Correlate local logon events with subsequent Connext service instability to identify suspicious authenticated activity.

Monitoring Recommendations

  • Forward operating system audit logs and Connext service logs to a centralized SIEM for retention and correlation.
  • Track integrity of binaries and configuration files under Connext installation directories using file integrity monitoring.
  • Alert on new local accounts or privilege changes on hosts running Connext Professional services.

How to Mitigate CVE-2026-2674

Immediate Actions Required

  • Upgrade RTI Connext Professional to version 7.7.0 or later for the 7.4.x branch.
  • Upgrade to 7.3.1.3 or later for the 7.0.0–7.3.x branch.
  • Plan migration off the 6.1.x branch, as it falls within the affected range with no fixed sub-version listed.
  • Restrict local access to hosts running Queueing Service, Persistence Service, or applications linked against Connext Core Libraries.

Patch Information

RTI has published fixed releases addressing the out-of-bounds write conditions. Consult the RTI Vulnerability Overview for the authoritative list of fixed versions and component-specific remediation guidance.

Workarounds

  • Limit local logon rights on systems hosting Connext services to a minimal set of administrative accounts.
  • Run Connext services under dedicated low-privilege service accounts isolated from interactive users.
  • Apply host-based access controls and process isolation to reduce the local attack surface until patches are deployed.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.