Skip to content
VulniPulse
High 2 vendors · 2 advisories

CVE-2026-92560: Apache Qpid Broker-J: Type size/count handling can lead to excessive allocation pre-authentication in the AMQP 0-10 decoder

CVE-2026-92560 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
High
CVSS base score
7.5 (Apache), 7.5 (Red Hat)
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H · base score 7.5, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: none. Availability impact: high.
Weakness
  • CWE-770 Allocation of resources without limits or throttling
EPSS
0.53% chance of exploitation in the next 30 days (45th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
Fixed releases
  • Apache: 10.1.1
  • Red Hat: 10.1.1
Vendor advisories
2 from Apache, Red Hat
Assigned by
apache (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-92560; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

A pre-authentication attacker could leverage type size/count handling to cause excessive allocation leading to potential denial of service. This issue affects Apache Qpid Broker-J: through 10.1.0. Users are recommended to upgrade to version 10.1.1, which fixes the issue.

Text from the CVE.org record (apache).

How do I fix CVE-2026-92560?

Upgrade to a fixed release named by the vendor:

  • Apache: 10.1.1
  • Red Hat: 10.1.1
  • Users are recommended to upgrade to version 10.1.1, which fixes the issue. (Apache)
  • Restrict access to the AMQP broker service port (default TCP port 5672 or 5671) to trusted networks or localhost using firewall controls. To limit access to authorized client subnets using firewalld: 1. Remove unrestricted public access to the AMQP port: # firewall-cmd --zone=public --remove-port=5672/tcp --permanent 2. Allow access only from trusted source IP addresses or subnets: # firewall-cmd --zone=trusted --add-source= --permanent 3. Apply the firewall configuration: # firewall-cmd --reload Caveat: Blocking public broker port access will prevent any external or unlisted clients from connecting to the messaging service. Verify that all legitimate application endpoints and client networks are added to the trusted zone. Warning: Reloading firewall rules may temporarily disrupt active network sessions or client connections. (Red Hat)

Vendor advisories for CVE-2026-92560

Apache

1 advisory

Red Hat

1 advisory
  • Advisory severityHigh7.5

    High [CVE-2026-92560] org.apache.qpid/qpid-broker-plugins-amqp-0-10-protocol: Apache Qpid Broker-J: Denial of Service via excessive memory allocation in AMQP 0-10 decoder

    CVE-2026-92560Source published Source updated

    A pre-authentication attacker could leverage type size/count handling to cause excessive allocation leading to potential denial of service. This issue affects Apache Qpid Broker-J: through 10.1.0. Users are recommended to upgrade to version 10.1.1, which fixes the issue. An unauthenticated remote attacker could exploit improper type size and count handling by sending specially crafted network messages. This can trigger excessive memory allocation, resulting in a Denial of Service (DoS) due to resource exhaustion. This vulnerability is rated as having Important impact because an unauthenticated remote attacker can trigger unbounded memory allocation, leading to process exhaustion and service termination without requiring authentication. In Red Hat environments such as Red Hat JBoss Fuse…

    Affected products in this advisory
    No product details extracted. Check the source bulletin.
    Source-reported affected versions
    • 10.1.0
    Source-reported fixed versions
    • 10.1.1
    Mitigation guidance
    • Restrict access to the AMQP broker service port (default TCP port 5672 or 5671) to trusted networks or localhost using firewall controls. To limit access to authorized client subnets using firewalld: 1. Remove unrestricted public access to the AMQP port: # firewall-cmd --zone=public --remove-port=5672/tcp --permanent 2. Allow access only from trusted source IP addresses or subnets: # firewall-cmd --zone=trusted --add-source=<TRUSTED_IP_OR_CIDR> --permanent 3. Apply the firewall configuration: # firewall-cmd --reload Caveat: Blocking public broker port access will prevent any external or unlisted clients from connecting to the messaging service. Verify that all legitimate application endpoints and client networks are added to the trusted zone. Warning: Reloading firewall rules may temporarily disrupt active network sessions or client connections.

References

Timeline

  1. CVE record published
  2. First vendor advisory listed by VulniPulse
  3. CVE record last updated

All Apache advisories

Get an email when Apache publishes the next one.

See Apache's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache