cve.bz

CVE-2026-67592 apache qpid protonj2

7.5 highEPSS 0.7%

High (7.5) in apache qpid protonj2. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
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

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-08-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-67592 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-67592?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-67592?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-67592 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-67592

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-67592](https://cve.bz/cve/badge/CVE-2026-67592.svg)](https://cve.bz/cve/CVE-2026-67592)

HTML:

<a href="https://cve.bz/cve/CVE-2026-67592"><img src="https://cve.bz/cve/badge/CVE-2026-67592.svg" alt="CVE-2026-67592"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Qpid ProtonJ2through 1.1.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 moreqpid-protonno fix listedUBUNTU-CVE-2026-67592

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is evaluated with a Moderate severity rating because exploitation requires established authentication, restricting the blast radius strictly to service availability rather than data confidentiality or integrity. Within Red Hat AMQ environments utilizing the ProtonJ2 library, an authenticated remote peer can transmit an unbounded stream of message transfer frames within an incoming delivery, which can exhaust Java heap memory and lead to a denial of service. The risk is constrained to authenticated communication channels, meaning unauthenticated network users cannot directly trigger this condition.

ProductPackageStateAdvisory
Red Hat AMQ Clientsprotonj2Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-67592.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON