Skip to main content
VulnerabilityPublished

CVE-2026-67592: Apache Qpid ProtonJ2 · Unthrottled Resource Allocation

Affects Apache Qpid ProtonJ2Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High · fixed in 1.2.0 : patch Apache Qpid ProtonJ2 soon.

Data as of 3 Nov 2026, 22:58 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.2.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Apache Software FoundationApache Qpid ProtonJ2Affected
  • <=1.1.0
Fixed in–
MavenApache Software Foundation/org.apache.qpid:protonj2pkg:maven/Apache Software Foundation/org.apache.qpid:protonj2Other threatsAffected
  • <=1.1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users are recommended to upgrade Apache Qpid ProtonJ2 to version 1.2.0 or later, where this issue is fixed. No other mitigation or temporary workaround is indicated.

Description

It was not possible to govern the maximum number of transfer frames per incoming delivery, enabling an authenticated attacker to cause excessive resource usage and 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

References

Community reviews

Loading reviews…