dbcve.org
Connext ProfessionalApplication · Rti

CVE-2026-2394

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 7.3.1.1 / 7.7.0 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Buffer Over-read vulnerability in RTI Connext Professional (Core Libraries) allows Overread Buffers.This issue affects Connext Professional: from 7.4.0 before 7.7.0, from 7.0.0 before 7.3.1.1, from 6.1.0 before 6.1.2.34, from 6.0.0 before 6.0.*, from 5.3.0 before 5.3.*, from 4.3x before 5.2.*.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A buffer over-read vulnerability exists in RTI Connext Professional Core Libraries that allows reading data beyond the intended buffer boundaries. This could enable an attacker to potentially read sensitive memory contents or cause a denial of service. The vulnerability affects multiple version branches of the Connext Professional middleware.

MitigationUpgrade to the patched version within your applicable branch (7.7.0+, 7.3.1.1+, 6.1.2.34+, or the patched versions in 6.0.x, 5.3.x, and 5.2.x). If immediate patching is not feasible, implement network segmentation to limit exposure to untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Connext ProfessionalApplication
Affected:>= 4.3.0, <= 5.2.3>= 5.3.0, <= 5.3.1.45>= 6.0.0, <= 6.0.1.40>= 6.1.0, <= 6.1.2.27>= 7.0.0, < 7.3.1.1>= 7.4.0, < 7.7.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate RTI Connext installation directory
    Search for directories containing 'rti' or 'Connext' in common installation paths such as /opt/rti, C:\Program Files\RTI, or /usr/local/rti. Also check user home directories for rti_connext_professional installations.
    Affected if RTI Connext Professional is installed on the system
  2. Identify installed Connext version from directory or version file
    Examine the installation folder name which typically includes the version number (e.g., rti_connext_professional-6.1.0). Alternatively, look for a VERSION.txt or rti-version.xml file in the installation root directory.
    Affected if Version number matches any of the affected ranges: 4.3.0-5.2.3, 5.3.0-5.3.1.45, 6.0.0-6.0.1.40, 6.1.0-6.1.2.27, 7.0.0-7.3.1.1, or 7.4.0-7.7.0
  3. Check NDDS or Connext library files for version metadata
    Use system tools to inspect the libnddscore.so, nddscore.so, or NDDSCore.dll shared libraries in the lib folder. Run 'strings' on Linux or use file properties on Windows to look for version strings embedded in the binaries.
    Affected if The library version matches any affected range listed above
  4. Verify running Connext-based applications or services
    Check for processes using RTI Connext libraries by running 'ps aux | grep -i rti' on Linux or examining loaded DLLs with Task Manager on Windows. Look for NDDSConfig.xml or USER_QOS_PROFILES.xml configuration files in the system.
    Affected if Connext middleware is actively loaded or configured for use in the environment

The environment is affected if RTI Connext Professional is installed and the installed version falls within any of the vulnerable ranges: 4.3.0 through 5.2.3, 5.3.0 through 5.3.1.45, 6.0.0 through 6.0.1.40, 6.1.0 through 6.1.2.27, 7.0.0 through 7.3.1.1, or 7.4.0 through 7.7.0.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.3.1.1 / 7.7.0 or later
Fixed in 7.3.1.17.7.0
Interim mitigation

Upgrade to the patched version within your applicable branch (7.7.0+, 7.3.1.1+, 6.1.2.34+, or the patched versions in 6.0.x, 5.3.x, and 5.2.x). If immediate patching is not feasible, implement network segmentation to limit exposure to untrusted networks.

Recommended fix High confidence

RTI Connext Professional 6.1.2.34 (or latest 6.0.x/5.3.x/5.2.x patch per your branch)

  1. 1. Identify the currently installed RTI Connext Professional version using the 'rtiddsgen -version' command or checking the installation directory.
  2. 2. For systems running version 6.1.0 through 6.1.2.27, upgrade to version 6.1.2.34 which contains the security fix.
  3. 3. For systems running version 6.0.0 through 6.0.1.40, upgrade to the latest 6.0.x patch release (6.0.1.41 or later if available).
  4. 4. For systems running version 5.3.0 through 5.3.1.45, upgrade to the latest 5.3.x patch release.
  5. 5. For systems running version 4.3.0 through 5.2.3, upgrade to the latest 5.2.x patch release.
  6. 6. After upgrading, restart any Connext applications and verify normal operation.
  7. 7. Consult RTI's release notes for any additional migration notes specific to your version jump.
Caveat Minor - this is a patch within the same major.minor branch; however, always review release notes for any behavior changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Connext Professional Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2394 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2394 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data