Skip to main content
VulnerabilityPublished Updated

CVE-2026-66274: Apache Qpid Proton-J · Unbounded type nesting can lead to pre-authentication stackoverflow

Affects org.apache.qpid:proton-jSource GCVE Database

0
Compare
Authoritative record:CVE-2026-66274· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 0.35.0 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 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.35.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

Upgrade org.apache.qpid:proton-j to 0.35.0.

Affected software

ProductAffectedFixed in
Mavenorg.apache.qpid:proton-jAffected
  • <0.35.0
Fixed in
  • 0.35.0

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

AI-suggested

Users should upgrade Apache Qpid Proton-J to version 0.35.0 or later, where this issue is fixed. Since a patch is available, applying the official fix is the recommended mitigation.

Description

Apache Qpid Proton-J versions prior to 0.35.0 contain a vulnerability where unbounded type nesting can cause a StackOverflowError before authentication. This flaw can be exploited by an attacker to cause a denial of service. The issue is fixed in version 0.35.0.

References

Community reviews

Loading reviews…