Service interruption via excessive type allocation
Published Aug 5, 2026 · Updated Aug 5, 2026
Excessive allocation in Apache Qpid ProtonJ2 1.1.0 and earlier allows remote attackers to interrupt dependent services before authentication. Apache has disclosed only that AMQP type size/count handling permits excessive allocation; it has not identified the affected decoder or operation. Exploitation requires an application to expose ProtonJ2 parsing to an untrusted AMQP peer, and memory exhaustion can halt that application.
Summary
What happened
Excessive allocation in Apache Qpid ProtonJ2 1.1.0 and earlier allows remote attackers to interrupt dependent services before authentication. Apache has disclosed only that AMQP type size/count handling permits excessive allocation; it has not identified the affected decoder or operation. Exploitation requires an application to expose ProtonJ2 parsing to an untrusted AMQP peer, and memory exhaustion can halt that application.
The record
- CVE
- CVE-2026-67589
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Qpid ProtonJ2
- Classifications
- CWE-789, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 5, 2026CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo