CVE-2026-67589 json
Apache Qpid ProtonJ2: Type size/count handling can lead to excessive allocation pre-authentication
published 2026-08-05 3 mo ago modified 2026-10-24 15 d ago also EUVD-2026-53035
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
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 ProtonJ2: through 1.1.0.
Users are recommended to upgrade to version 1.2.0, which fixes the issue.
Patch / fix
- apache qpid_protonj2 1.2.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-67589 updated cvss 7.5
org.apache.qpid/protonj2: Apache Qpid ProtonJ2: Denial of Service via excessive memory allocation
-
Red Hat AMQ Clients 2026.Q3fixed: vendor fix RHSA-2026:69459
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.77% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Apache Software Foundation Apache Qpid ProtonJ2
Classification
- Weakness
-
- CWE-789 Memory Allocation with Excessive Size Value
References
-
lists.apache.org
/thread/bs24x4778dh72xtfs299cy8krvdlo47q
vendor-advisory
-
openwall.com
/lists/oss-security/2026/08/04/28
third-party-advisory
Sources
- CVE List CVE-2026-67589
- NVD CVE-2026-67589
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.