CVE-2026-72418: Software Security Vulnerability Vulnerability

HIGH

Advisory Identifier: GHSA-prxp-6xjx-9qx5

CVSS 7.5

Published 2026-08-15

Advisory Summary

CVE-2026-72418 is a HIGH (CVSS 7.5) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-72418 at a Glance

CVE Identifier CVE-2026-72418

GHSA Identifier GHSA-prxp-6xjx-9qx5

Severity HIGH

CVSS v3.1 Base Score 7.5

CWE Classification General Security Weakness

Affected Product Software

Package Ecosystem Maven

Published Date 2026-08-15

Last Updated 2026-08-17

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-72418

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-72418, 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 General Security Weakness. 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

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conncount: prevent connlimit drops for early confirmed ct Commit 69894e5b4c5e ("netfilter: nft_connlimit: update the count if add was skipped") introduced a regression where packets for valid connections are dropped when using connlimit for soft-limiting scenarios. The issue occurs when a new connection reuses a socket currently in the TIME_WAIT state. In this scenario, the connection tracking entry is evaluated as already confirmed. Previously, __nf_conncount_add() assumed that if a connection was confirmed and did not originate from the loopback interface, it should skip the addition and return -EEXIST. Skipping the addition triggers a garbage collection run that cleans up the TIME_WAIT connection. Consequently, the active connection count drops to 0, which xt_connlimit mishandles, leading to the false rejection of the perfectly valid new connection. Fix this by replacing the interface check with protocol-agnostic state checks. We now skip the tree insertion and preserve the lockless garbage collection optimization only if the connection is IPS_ASSURED. This allows early-confirmed setup packets (such as reused TIME_WAIT sockets or locally generated SYN-ACKs) to be properly evaluated and counted without falsely dropping. The goto check_connections path is maintained to ensure these setup packets are deduplicated correctly. This has been tested with slowhttptest and HTTP server configured locally to ensure we are not breaking soft-limiting scenarios for local or external connections. In addition, it was tested with a OVS zone limit too.

References

NVD — CVE-2026-72418 NVD

https://nvd.nist.gov/vuln/detail/CVE-2026-72418

git.kernel.org/stable/c/000ac6830b... WEB

https://git.kernel.org/stable/c/000ac6830b56499d6b65fd91486ce6689eb02be4

git.kernel.org/stable/c/329f2626ee... WEB

https://git.kernel.org/stable/c/329f2626ee5cb8fafdf6b58b624311529c57cb45

git.kernel.org/stable/c/3793d24de2... WEB

https://git.kernel.org/stable/c/3793d24de224943e0a6016bbeffb6f5c4cea2e3d

git.kernel.org/stable/c/abef7f8172... WEB

https://git.kernel.org/stable/c/abef7f817217fcb62c11821d6b895063eadb2828

git.kernel.org/stable/c/be52572c6d... WEB

https://git.kernel.org/stable/c/be52572c6d55f677ba76869d3c63805c0d4891a3

git.kernel.org/stable/c/c8b6f36f76... WEB

https://git.kernel.org/stable/c/c8b6f36f766991e3ebebec6596daee4b04dcbc49

git.kernel.org/stable/c/cbe2d14a7c... WEB

https://git.kernel.org/stable/c/cbe2d14a7c5b1fc71821fbfee5c4963917411e92

git.kernel.org/stable/c/ebfe8249ba... WEB

https://git.kernel.org/stable/c/ebfe8249ba79e4ff0f1e3aad8787b992ef27f026

Frequently Asked Questions

What is CVE-2026-72418?

CVE-2026-72418 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.

Which Software versions are affected?

Affected versions include releases prior to current release patches.

What version fixes CVE-2026-72418?

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-72418?

CVE-2026-72418 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-72418?

CVE-2026-72418 is classified under General Security Weakness.

How can I check Maven dependencies for CVE-2026-72418?

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-prxp-6xjx-9qx5",
  "modified" : "2026-08-17T06:33:28Z",
  "published" : "2026-08-15T06:32:23Z",
  "aliases" : [ "CVE-2026-72418" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_conncount: prevent connlimit drops for early confirmed ct\n\nCommit 69894e5b4c5e (\"netfilter: nft_connlimit: update the count if add\nwas skipped\") introduced a regression where packets for valid\nconnections are dropped when using connlimit for soft-limiting\nscenarios.\n\nThe issue occurs when a new connection reuses a socket currently in\nthe TIME_WAIT state. In this scenario, the connection tracking entry\nis evaluated as already confirmed. Previously, __nf_conncount_add()\nassumed that if a connection was confirmed and did not originate from\nthe loopback interface, it should skip the addition and return -EEXIST.\n\nSkipping the addition triggers a garbage collection run that cleans up\nthe TIME_WAIT connection. Consequently, the active connection count\ndrops to 0, which xt_connlimit mishandles, leading to the false rejection\nof the perfectly valid new connection.\n\nFix this by replacing the interface check with protocol-agnostic state\nchecks. We now skip the tree insertion and preserve the lockless garbage\ncollection optimization only if the connection is IPS_ASSURED. This\nallows early-confirmed setup packets (such as reused TIME_WAIT sockets\nor locally generated SYN-ACKs) to be properly evaluated and counted\nwithout falsely dropping. The goto check_connections path is maintained\nto ensure these setup packets are deduplicated correctly.\n\nThis has been tested with slowhttptest and HTTP server configured\nlocally to ensure we are not breaking soft-limiting scenarios for local\nor external connections. In addition, it was tested with a OVS zone\nlimit too.",
  "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-72418"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/000ac6830b56499d6b65fd91486ce6689eb02be4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/329f2626ee5cb8fafdf6b58b624311529c57cb45"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3793d24de224943e0a6016bbeffb6f5c4cea2e3d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/abef7f817217fcb62c11821d6b895063eadb2828"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/be52572c6d55f677ba76869d3c63805c0d4891a3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c8b6f36f766991e3ebebec6596daee4b04dcbc49"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cbe2d14a7c5b1fc71821fbfee5c4963917411e92"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ebfe8249ba79e4ff0f1e3aad8787b992ef27f026"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:15Z"
  }
}

CVSS V3

7.5 HIGH