dbcve.org
Connext ProfessionalApplication · Rti

CVE-2026-2674

HIGH · 8.1 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to 7.7.0 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
Out-of-bounds Write, Out-of-bounds Write, Out-of-bounds Write vulnerability in RTI Connext Professional (Queueing Service,Core Libraries,Persistence Service) allows Overflow Buffers, Overflow Buffers, Overflow Buffers.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.*.

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 · moderate confidence

Out-of-bounds write vulnerability in RTI Connext Professional (Queueing Service, Core Libraries, Persistence Service) allows writing beyond allocated buffer boundaries. This memory corruption flaw could enable remote code execution or denial of service via specially crafted network messages.

MitigationUpgrade to RTI Connext Professional 7.7.0 or later, or apply vendor patches for affected 7.x and 6.x versions. Review and restrict network exposure of affected Connext services until patches are applied.

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:>= 6.1.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

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. Identify installed RTI Connext Professional version
    Locate the RTI Connext Professional installation and determine its version number. This is typically available via the product's documentation, installer metadata, or by querying the installed software on the system.
    Affected if The version is found to be 6.1.0 or higher but lower than 7.7.0
  2. Confirm affected components are in use
    Determine whether any of the following components are installed and operational: Queueing Service, Core Libraries, or Persistence Service. These are the components containing the vulnerability.
    Affected if Any of these three components (Queueing Service, Core Libraries, or Persistence Service) are present in the environment
  3. Assess network exposure of Connext services
    Review network configuration and firewall rules to determine if the affected Connext services are accessible over the network. The vulnerability is exploitable via specially crafted network messages.
    Affected if The affected services are exposed to untrusted network segments or external hosts
  4. Check for running Connext service processes
    Identify any running processes corresponding to Queueing Service or Persistence Service on the system using standard process inspection tools.
    Affected if Queueing Service or Persistence Service processes are actively running and listening on network ports

The environment is affected if RTI Connext Professional version 6.1.0 through 7.6.x is installed with Queueing Service, Core Libraries, or Persistence Service exposed to network traffic.

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.7.0 or later
Fixed in 7.7.0
Interim mitigation

Upgrade to RTI Connext Professional 7.7.0 or later, or apply vendor patches for affected 7.x and 6.x versions. Review and restrict network exposure of affected Connext services until patches are applied.

Recommended fix High confidence

RTI Connext Professional 7.7.0 or later

  1. 1. Identify the current installed version of RTI Connext Professional by checking the installation directory or running the version command
  2. 2. Download RTI Connext Professional version 7.7.0 or later from the official RTI website (www.rti.com)
  3. 3. Review the RTI Connext Professional migration guide for version 7.7.0 to understand any configuration or API changes
  4. 4. Back up all existing RTI configuration files, XML profiles, and persistent data
  5. 5. Stop all running RTI services (Queueing Service, Persistence Service) and applications using Connext libraries
  6. 6. Install version 7.7.0 or later following the RTI installation documentation
  7. 7. Restore or migrate configuration files as needed based on migration guide
  8. 8. Restart RTI services and verify they start correctly
Caveat Major version upgrade from 6.1.x to 7.7.0 may introduce API and configuration changes; review migration guide for backward compatibility considerations

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

Fix this in Connext Professional Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2674 — 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-2674 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