RTI Connext Updates Address Nineteen Vulnerabilities

P1 — VALIDATE AND UPDATELow to Critical · 3.3 / 4.7 / 5.3 / 5.5 / 6.5 / 7.0 / 7.1 / 7.4 / 7.5 / 7.8 / 8.1 / 8.8 / 9.8 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

The authority published RTI-SB-2026-09 for RTI Connext Professional and Connext AUTOSAR Toolkit. RTI published branch-specific fixes for memory-safety, validation, disclosure, denial-of-service, and code-execution risks. Exact applicability differs by CVE and architecture. Affected deployments should be matched to the authority's exact scope and moved to the supported fixed release.

Confirm Scope And Apply The Supported Fix

What to do now: Inventory RTI Connext Professional and Connext AUTOSAR Toolkit, match the exact affected release or feature, apply the authority-supported fixed build or service remediation, validate the dependent workflow, and preserve evidence.

Open the authoritative advisory

Last verified: 2026-09-23 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeRTI Connext Professional and Connext AUTOSAR Toolkit
AdvisoryRTI-SB-2026-09
CVEsCVE-2025-70873, CVE-2026-11388, CVE-2026-11389, CVE-2026-18457, CVE-2026-18458, CVE-2026-18459, CVE-2026-18460, CVE-2026-18461, CVE-2026-18462, CVE-2026-18626, CVE-2026-34180, CVE-2026-34480, CVE-2026-41080, CVE-2026-45186, CVE-2026-45447, CVE-2026-56132, CVE-2026-56407, CVE-2026-7866, CVE-2026-8849
Authoritative release date2026-09-22 17:50:13.857 UTC
Authority revision date2026-09-22 17:50:13.857 UTC
Affected versionsConnext Professional 4.1x through versions before 7.7.0.1 and Connext AUTOSAR Toolkit 2.0.0 through versions before 4.0.1.1, subject to the per-CVE table
Fixed versionConnext Professional 7.3.1.6 or 7.7.0.1 and AUTOSAR Toolkit 4.0.1.1; contact RTI Support for other supported versions and architectures
CVSS base score3.3 / 4.7 / 5.3 / 5.5 / 6.5 / 7.0 / 7.1 / 7.4 / 7.5 / 7.8 / 8.1 / 8.8 / 9.8 (CVSS v3.1)
CVSS severityLow to Critical
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

RTI published branch-specific fixes for memory-safety, validation, disclosure, denial-of-service, and code-execution risks. Exact applicability differs by CVE and architecture.

What To Validate Now

  1. Inventory. Locate RTI Connext Professional and Connext AUTOSAR Toolkit deployments, versions, enabled features, exposure paths, owners, and dependent services.
  2. Establish applicability. Compare each deployment with the authority's affected-version statement: Connext Professional 4.1x through versions before 7.7.0.1 and Connext AUTOSAR Toolkit 2.0.0 through versions before 4.0.1.1, subject to the per-CVE table Do not infer applicability from product family or severity alone.
  3. Remediate. Apply Connext Professional 7.3.1.6 or 7.7.0.1 and AUTOSAR Toolkit 4.0.1.1; contact RTI Support for other supported versions and architectures through the supported vendor or project channel, following the current advisory and change-control requirements.
  4. Validate. Confirm the resulting version or managed-service state, exercise representative functionality and recovery paths, monitor for regressions, and document exceptions.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.