dbcve.org
Connext ProfessionalApplication · Rti

CVE-2025-4582

HIGH · 7.1 CVSS v3.1 Published 2025-09-23
Fix available
A fix is available. Upgrade to 6.1.2.26 / 7.3.0.8 or later.
See remediation →
73/100
Remediation priority · Elevated
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, Off-by-one Error vulnerability in RTI Connext Professional (Core Libraries) allows File Manipulation, Overread Buffers.This issue affects Connext Professional: from 7.4.0 before 7.6.0, from 7.0.0 before 7.3.0.8, from 6.1.0 before 6.1.2.26, from 6.0.0 before 6.0.1.43, from 5.3.0 before 5.3.*, from 4.4a 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 · moderate confidence

A buffer over-read vulnerability in RTI Connext Professional Core Libraries allows reading beyond allocated buffer boundaries due to an off-by-one error. This could enable attackers to manipulate files or read sensitive memory contents through specially crafted input to the middleware's data distribution components.

MitigationUpgrade RTI Connext Professional to version 7.6.0 or later, 7.3.0.8 or later, 6.1.2.26 or later, 6.0.1.43 or later, or the latest 5.3.x/5.2.x patch release per the version branch affected.

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.4a, < 6.1.2.26>= 7.0.0, < 7.3.0.8>= 7.4.0, < 7.6.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Locate RTI Connext installation directory
    Check common installation paths such as C:\Program Files\RTI\Connext (Windows) or /opt/rti_connext (Linux). Also check for environment variable RTI_DIR if set.
    Affected if RTI Connext Professional is installed on the system
  2. Identify core library version
    Look for version information in the installed core library files (nddscore.dll on Windows or libnddscore.so on Linux) located in the lib or bin directory of the Connext installation. Use file properties or strings command to extract version metadata.
    Affected if The core library version cannot be determined or is not visible
  3. Compare installed version against affected ranges
    Extract the exact version number (for example 6.1.0, 7.2.1, 7.4.0) and compare to the vulnerable ranges: 4.4a to 6.1.2.25, 7.0.0 to 7.3.0.7, or 7.4.0 to 7.5.x
    Affected if Installed version falls within any of these ranges: >= 4.4a and < 6.1.2.26, OR >= 7.0.0 and < 7.3.0.8, OR >= 7.4.0 and < 7.6.0
  4. Check if Connext applications run
    Identify any DDS participant applications, publishers, or subscribers that use the installed Connext libraries. Check running processes or startup scripts that load the core libraries.
    Affected if Applications using the affected Connext libraries are deployed or running

If RTI Connext Professional is installed and the version falls within any of the three affected ranges (4.4a to 6.1.2.25, 7.0.0 to 7.3.0.7, or 7.4.0 to 7.5.x), the environment is vulnerable to the buffer over-read flaw in the core libraries.

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 6.1.2.26 / 7.3.0.8 / 7.6.0 or later
Fixed in 6.1.2.267.3.0.87.6.0
Interim mitigation

Upgrade RTI Connext Professional to version 7.6.0 or later, 7.3.0.8 or later, 6.1.2.26 or later, 6.0.1.43 or later, or the latest 5.3.x/5.2.x patch release per the version branch affected.

Recommended fix High confidence

Upgrade to 7.6.0 (or 6.1.2.26/7.3.0.8 depending on current major version branch)

  1. 1. Identify the currently installed RTI Connext Professional version using 'rtiddsversion' or checking installation directories
  2. 2. Based on current version, determine the appropriate upgrade path: if on 6.1.x branch upgrade to 6.1.2.26, if on 7.0.x-7.2.x upgrade to 7.3.0.8, if on 7.4.x-7.5.x upgrade to 7.6.0
  3. 3. Backup all existing Connext configurations, XML files, and persistent data
  4. 4. Download the appropriate fixed release from the RTI Customer Portal at rti.com
  5. 5. Stop all running Connext applications and services
  6. 6. Install the upgraded version following RTI installation documentation
  7. 7. Restore configurations from backup
  8. 8. Restart Connext applications and verify functionality
Caveat Review RTI release notes for migration notes; newer major versions may have API or configuration changes

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

Fix this in Connext Professional Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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