# CVE-2025-7464: osrg GoBGP rtr.go SplitRTR out-of-bounds

> Remote attackers can trigger an out-of-bounds read in GoBGP's RTR packet processing, potentially causing crashes or leaking memory.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jul 2025
- **Updated:** 14 Jul 2025
- **Also known as:** DEBIAN-CVE-2025-7464, GHSA-vwjp-r23f-3f37, UBUNTU-CVE-2025-7464

## What is CVE-2025-7464?

CVE-2025-7464 is a medium-severity memory corruption vulnerability in osrg GoBGP, published on 12 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability classified as problematic has been found in osrg GoBGP up to 3.37.0. Affected is the function SplitRTR of the file pkg/packet/rtr/rtr.go. The manipulation leads to out-of-bounds read. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The name of the patch is e748f43496d74946d14fed85c776452e47b99d64. It is recommended to apply a patch to fix this issue.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

Apply the vendor's patch.

## Is CVE-2025-7464 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7464 is a medium-severity memory corruption vulnerability in osrg GoBGP, published on 12 Jul 2025. 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-2025-7464 in the wild and no public exploit code.

Affected product: osrg GoBGP. 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-7464/ (Markdown: https://insights.sbomify.com/CVE-2025-7464/index.md)
```

## Sources

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

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