# CVE-2026-18460: Memory corruption in Connext Professional

> An off-by-one error in RTI Connext Professional Core Libraries allows out-of-bounds writes, potentially leading to buffer overflows and code execution.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-ghvx-mjwc-5386

## What is CVE-2026-18460?

CVE-2026-18460 is a medium-severity memory corruption vulnerability in RTI Connext Professional, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Off-by-one Error, Out-of-bounds Write vulnerability in RTI Connext Professional (Core Libraries) allows Overflow Buffers. This issue affects Connext Professional: from 7.4.0 before 7.7.0.1, from 7.0.0 before 7.3.1.6.

Weakness: CWE-787 (Out-of-bounds Write), CWE-193 (Off-by-one Error)

## Which versions are affected by CVE-2026-18460?


## How do I fix CVE-2026-18460?

No fix has been published for CVE-2026-18460 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-18460 being exploited?

There is no known exploitation of CVE-2026-18460 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-18460 and fix it if it is affected.

What it is: CVE-2026-18460 is a medium-severity memory corruption vulnerability in RTI Connext Professional, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18460 in the wild and no public exploit code.

Affected product: RTI Connext Professional. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-18460/ (Markdown: https://insights.sbomify.com/CVE-2026-18460/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-18460
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-18460
- OSV: https://osv.dev/vulnerability/CVE-2026-18460

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-18460/
Summaries are generated and may contain mistakes; the official description above is the record.