How severe is CVE-2026-77410?

CVE-2026-77410 has a CVSS 4.0 base score of 8.9, rated high severity.

Is CVE-2026-77410 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (35th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-77410?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-77410 published?

CVE-2026-77410 was published on 2026-09-16.

CVE-2026-77410

CVE-2026-77410 is a high-severity vulnerability with a CVSS 4.0 base score of 8.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-789.

Key facts

Severity: High (CVSS 4.0 base score 8.9)
EPSS exploit prediction: 0% (35th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-789
Published: 2026-09-16
Last modified: 2026-09-16

Description

RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.recvContent in channel.go preallocates the message body slice with the uint64 ch.header.Size value supplied by an AMQP content header without capping the allocation to the negotiated Connection.Config.FrameSize value. A malicious or compromised broker can send an extreme declared body size and cause the Go runtime to attempt a correspondingly large allocation before body data is received. The allocation can exhaust memory and terminate the client process. This issue is fixed in version 1.13.0.

Frequently asked questions

What is CVE-2026-77410?: RabbitMQ amqp091-go is a Go AMQP 0.9.1 client. Prior to 1.13.0, Channel.recvContent in channel.go preallocates the message body slice with the uint64 ch.header.Size value supplied by an AMQP content header without capping the allocation to the negotiated Connection.Config.FrameSize value. A malicious or compromised broker can send an extreme declared body size and cause the Go runtime to attempt a correspondingly large allocation before body data is received. The allocation can exhaust memory and terminate the client process. This issue is fixed in version 1.13.0.
How severe is CVE-2026-77410?: CVE-2026-77410 has a CVSS 4.0 base score of 8.9, rated high severity.
Is CVE-2026-77410 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (35th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-77410?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-77410 published?: CVE-2026-77410 was published on 2026-09-16.

References

Other CWE-789 vulnerabilities

CVE-2026-82435 — Critical (CVSS 9.8): Description The worker's Netty message decoder is installed ahead of the SASL authentication handlers in the…
CVE-2021-34869 — High (CVSS 8.8): This vulnerability allows local attackers to escalate privileges on affected installations of Parallels Desktop…
CVE-2021-34868 — High (CVSS 8.8): This vulnerability allows local attackers to escalate privileges on affected installations of Parallels Desktop…
CVE-2026-69219 — High (CVSS 8.7): The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes.…
CVE-2026-58067 — High (CVSS 8.7): A vulnerability in Veeam Service Provider Console allowing an unauthenticated attacker to exhaust host memory and cause…
CVE-2026-20295 — High (CVSS 8.6): A vulnerability in the sftunnel inter-device communication protocol of Cisco Secure FMC Software and Cisco Secure FTD…

Browse all CWE-789 vulnerabilities →