Authenticated service interruption via flow-control window exceedance
Published Aug 5, 2026 · Updated Aug 5, 2026
Denial of service in Apache Qpid ProtonJ2 1.1.0 and earlier allows remote authenticated users to interrupt AMQP services. Apache identifies the incoming session flow-control window as the affected locus but has not published the code path or validation error that permits it to be exceeded. An authenticated AMQP peer can trigger the condition, interrupting the embedding client or service without reported data disclosure or modification.
Summary
What happened
Denial of service in Apache Qpid ProtonJ2 1.1.0 and earlier allows remote authenticated users to interrupt AMQP services. Apache identifies the incoming session flow-control window as the affected locus but has not published the code path or validation error that permits it to be exceeded. An authenticated AMQP peer can trigger the condition, interrupting the embedding client or service without reported data disclosure or modification.
The record
- CVE
- CVE-2026-67591
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Qpid ProtonJ2
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- authenticated
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