# CVE-2026-88763: Skupper-router: skupper-router: unbounded recursion in amqp field parser leads to denial of service

> An attacker can crash the skupper-router by sending a crafted AMQP message, causing a denial of service for interconnected services.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Sep 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-j54j-r8q7-v2hq, RHSA-2026:82316

## What is CVE-2026-88763?

CVE-2026-88763 is a medium-severity denial of service vulnerability in Red Hat Service Interconnect 2 for RHEL 8, published on 10 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in the skupper-router component of Red Hat Service Interconnect, which is used to provide secure communication between distributed services. The issue occurs when the router processes a specially crafted network message using its AMQP field parser. Due to a lack of bounds on recursion during parsing, the router can run out of stack memory and crash, leading to a denial of service for the interconnected network.

Weakness: CWE-674 (Uncontrolled Recursion)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `skupper-router` | Red Hat:service_interconnect:2.0::el8 | All versions | 0:3.5.3-1.el8 |
| `skupper-router-common` | Red Hat:service_interconnect:2.0::el8 | All versions | 0:3.5.3-1.el8 |
| `skupper-router-debuginfo` | Red Hat:service_interconnect:2.0::el8 | All versions | 0:3.5.3-1.el8 |
| `skupper-router-debugsource` | Red Hat:service_interconnect:2.0::el8 | All versions | 0:3.5.3-1.el8 |
| `skupper-router-docs` | Red Hat:service_interconnect:2.0::el8 | All versions | 0:3.5.3-1.el8 |
| `skupper-router-tools` | Red Hat:service_interconnect:2.0::el8 | All versions | 0:3.5.3-1.el8 |
| `skupper-router` | Red Hat:service_interconnect:2.0::el9 | All versions | 0:3.5.3-1.el9 |
| `skupper-router-common` | Red Hat:service_interconnect:2.0::el9 | All versions | 0:3.5.3-1.el9 |
| `skupper-router-debuginfo` | Red Hat:service_interconnect:2.0::el9 | All versions | 0:3.5.3-1.el9 |
| `skupper-router-debugsource` | Red Hat:service_interconnect:2.0::el9 | All versions | 0:3.5.3-1.el9 |
| `skupper-router-docs` | Red Hat:service_interconnect:2.0::el9 | All versions | 0:3.5.3-1.el9 |
| `skupper-router-tools` | Red Hat:service_interconnect:2.0::el9 | All versions | 0:3.5.3-1.el9 |

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

Apply the vendor's patch.

## Is CVE-2026-88763 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88763 is a medium-severity denial of service vulnerability in Red Hat Service Interconnect 2 for RHEL 8, published on 10 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-88763 in the wild and no public exploit code.

Affected product: Red Hat Service Interconnect 2 for RHEL 8. 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-88763/ (Markdown: https://insights.sbomify.com/CVE-2026-88763/index.md)
```

## Sources

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

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