Skip to content
VulniPulse
Medium5.9Red Hat Linux

Medium [CVE-2026-88763] Unbounded recursion in AMQP field parser leads to denial of service

This medium-severity Red Hat Linux advisory covers CVE-2026-88763 affecting Red Hat Service Interconnect 2.

CVE-2026-88763 Published Sep 10, 2026Updated by vendor Sep 10, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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.

The Red Hat Product Security team has assessed the severity of this vulnerability as Moderate, given that exploitation requires the attacker to have a valid x.509 certificate signed by the internal network's certificate authority. Successful exploitation allows an attacker to crash the skupper-router process, leading to a denial of service.

The vulnerability's root cause is a lack of recursion depth limits in the AMQP field parsing logic. Weakness: CWE-674.

Affected Red Hat products: Red Hat Service Interconnect 2. Red Hat does not currently list a fixing RHSA for this CVE.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · medium-confidence parse· fetched 1 hour ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · medium-confidence parse· fetched 1 hour ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · medium-confidence parse· fetched 1 hour ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.