GO · SEPTEMBER 2026 · EARLY WARNING

amqp091-go Library Vulnerability: Memory Exhaustion Risk

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
Severity
HIGH
Affected component
amqp091-go (go)
Affected versions
< 1.13.0
Patched version
Not yet available
GHSA-6C5V-HQJR-5XXP

An early warning has been issued regarding a vulnerability in the amqp091-go client library. This issue may allow a compromised or malicious AMQP broker to force the client to process oversized payloads, potentially leading to memory exhaustion or denial of service.

What happened

An early warning has been issued for a vulnerability in the amqp091-go client library. This vulnerability reportedly allows a compromised or malicious AMQP broker to force the client to allocate resources for and process content body frames that exceed the negotiated frame_max limit. This can lead to unexpected memory consumption or application-layer denial of service (DoS), bypassing the protocol's built-in framing constraints.

The vulnerability affects versions of amqp091-go prior to 1.13.0. The issue is under investigation and no official fix has been published yet. Users of this library should monitor updates from the maintainers and consider using an alternative AMQP client library until a fix is released.

What to do about it

How 0Day would have caught this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If amqp091-go is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Frequently asked questions

Am I affected?

You may be affected if you are using the amqp091-go client library in versions prior to 1.13.0.

What should I do right now?

Monitor for updates from the maintainers of the amqp091-go library and consider using a different AMQP client library until a fix is released.

Is there an official fix available?

No official fix has been published yet. Continue to monitor the primary sources for updates.

Sources

Join the 0Day waitlist →

← Back to all threats