CVE-2026-34183: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-f5vx-f6jp-89j6
Share
CVSS 7.5
CWE-1325
Published
Advisory Summary

CVE-2026-34183 is a HIGH (CVSS 7.5) security vulnerability vulnerability (CWE-1325: Improperly Controlled Sequential Memory Allocation) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-34183 at a Glance

CVE Identifier CVE-2026-34183
GHSA Identifier GHSA-f5vx-f6jp-89j6
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-1325: Improperly Controlled Sequential Memory Allocation
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-34183

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-34183, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-1325: Improperly Controlled Sequential Memory Allocation, where the product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Issue summary: Remote peer may exhaust heap memory of the QUIC server or client by flooding it with packets containing PATH_CHALLENGE frames. Impact summary: A malicious remote peer can cause an unbounded memory allocation which can lead to an abnormal termination of the application acting as a QUIC client or server and a Denial of Service. A remote peer may exhaust heap memory by flooding the local QUIC stack with PATH_CHALLENGE frames. The local QUIC stack allocates a PATH_RESPONSE frame for every PATH_CHALLENGE it receives. The allocated PATH_RESPONSE frame gets freed only when the remote peer acknowledges reception of the PATH_RESPONSE frame which will not be done by a malicious peer. The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue. The QUIC stack is outside of OpenSSL FIPS module boundary.

References

NVD — CVE-2026-34183 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-34183
Security Fix Commit FIX COMMIT
https://github.com/openssl/openssl/commit/5b306efb0b3779dfdd0803b4afc9d08c91f11517
Security Fix Commit FIX COMMIT
https://github.com/openssl/openssl/commit/7d06955ebe0ecf8adfd4c1e92018586da47ef9ac
Security Fix Commit FIX COMMIT
https://github.com/openssl/openssl/commit/d2e9efbe4900a373227deb136e8665401404ffac
Security Fix Commit FIX COMMIT
https://github.com/openssl/openssl/commit/fbaa83859c01ad64f497b757aaf51be7d05ed9eb
Security Fix Commit FIX COMMIT
https://github.com/openssl/security/commit/5b306efb0b3779dfdd0803b4afc9d08c91f11517
Security Fix Commit FIX COMMIT
https://github.com/openssl/security/commit/7d06955ebe0ecf8adfd4c1e92018586da47ef9ac
Security Fix Commit FIX COMMIT
https://github.com/openssl/security/commit/d2e9efbe4900a373227deb136e8665401404ffac
Security Fix Commit FIX COMMIT
https://github.com/openssl/security/commit/fbaa83859c01ad64f497b757aaf51be7d05ed9eb
openssl-library.org/news/secadv/2026060... WEB
https://openssl-library.org/news/secadv/20260609.txt

Frequently Asked Questions

What is CVE-2026-34183?
CVE-2026-34183 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-1325: Improperly Controlled Sequential Memory Allocation.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-34183?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-34183?
CVE-2026-34183 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-34183?
CVE-2026-34183 is classified under CWE-1325: Improperly Controlled Sequential Memory Allocation (The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.).
How can I check Maven dependencies for CVE-2026-34183?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-f5vx-f6jp-89j6",
  "modified" : "2026-06-10T18:31:41Z",
  "published" : "2026-06-09T18:30:41Z",
  "aliases" : [ "CVE-2026-34183" ],
  "details" : "Issue summary: Remote peer may exhaust heap memory of the QUIC\nserver or client by flooding it with packets containing PATH_CHALLENGE\nframes.\n\nImpact summary: A malicious remote peer can cause an unbounded\nmemory allocation which can lead to an abnormal termination of the\napplication acting as a QUIC client or server and a Denial of Service.\n\nA remote peer may exhaust heap memory by flooding the local\nQUIC stack with PATH_CHALLENGE frames. The local QUIC stack\nallocates a PATH_RESPONSE frame for every PATH_CHALLENGE it receives.\nThe allocated PATH_RESPONSE frame gets freed only when the remote\npeer acknowledges reception of the PATH_RESPONSE frame which will\nnot be done by a malicious peer.\n\nThe FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by\nthis issue. The QUIC stack is outside of OpenSSL FIPS module\nboundary.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34183"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/openssl/commit/5b306efb0b3779dfdd0803b4afc9d08c91f11517"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/openssl/commit/7d06955ebe0ecf8adfd4c1e92018586da47ef9ac"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/openssl/commit/d2e9efbe4900a373227deb136e8665401404ffac"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/openssl/commit/fbaa83859c01ad64f497b757aaf51be7d05ed9eb"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/security/commit/5b306efb0b3779dfdd0803b4afc9d08c91f11517"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/security/commit/7d06955ebe0ecf8adfd4c1e92018586da47ef9ac"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/security/commit/d2e9efbe4900a373227deb136e8665401404ffac"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openssl/security/commit/fbaa83859c01ad64f497b757aaf51be7d05ed9eb"
  }, {
    "type" : "WEB",
    "url" : "https://openssl-library.org/news/secadv/20260609.txt"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1325" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-06-09T17:17:05Z"
  }
}