# CVE-2025-4582: Memory corruption in Connext Professional

> An off-by-one error in RTI Connext Professional core libraries allows attackers to overread buffers and manipulate files.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2025
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-mf34-h88r-wq9g

## What is CVE-2025-4582?

CVE-2025-4582 is a medium-severity memory corruption vulnerability in RTI Connext Professional, published on 23 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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 5.2.0 before 5.2.*, from 4.4a before 5.1.*.

Weakness: CWE-193 (Off-by-one Error), CWE-126 (Buffer Over-read)

## Which versions are affected by CVE-2025-4582?

It affects 1 product.


Products: Rti Connext Professional.

## How do I fix CVE-2025-4582?

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

## Is CVE-2025-4582 being exploited?

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

## Other vulnerabilities in RTI Connext Professional

- [CVE-2026-2467](https://insights.sbomify.com/CVE-2026-2467/): Memory corruption in Connext Professional (critical 9.2)
- [CVE-2026-3894](https://insights.sbomify.com/CVE-2026-3894/): Out-of-bounds Read vulnerability in RTI Connext Professional (Core Libraries) allows Overread Buffers. (critical 9.2)
- [CVE-2024-52057](https://insights.sbomify.com/CVE-2024-52057/): SQL injection in Connext Professional (critical 9.1)
- [CVE-2026-7300](https://insights.sbomify.com/CVE-2026-7300/): Memory corruption in Connext Professional (high 8.8)
- [CVE-2025-14543](https://insights.sbomify.com/CVE-2025-14543/): XML external entity in Connext Professional (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4582 and fix it if it is affected.

What it is: CVE-2025-4582 is a medium-severity memory corruption vulnerability in RTI Connext Professional, published on 23 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4582 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-2025-4582/ (Markdown: https://insights.sbomify.com/CVE-2025-4582/index.md)
```

## Sources

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

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