CVE-2026-72427: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-6pxh-c54r-cxc3
Share
CVSS 7.8
Published
Advisory Summary

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

CVE-2026-72427 at a Glance

CVE Identifier CVE-2026-72427
GHSA Identifier GHSA-6pxh-c54r-cxc3
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

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

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

How to Fix CVE-2026-72427

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-72427, 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: bpf: Fix effective prog array index with BPF_F_PREORDER replace_effective_prog() and purge_effective_progs() located the slot in the effective array by walking the program hlist and counting entries linearly. That count does not match the array layout: compute_effective_ progs() places BPF_F_PREORDER programs at the front (ancestor cgroup first, attach order within a cgroup) and the rest after them (descendant cgroup first). So when a preorder program is present, the linear hlist position no longer equals the program's index in the effective array. For replace_effective_prog() (bpf_link_update()) this overwrote the wrong slot, corrupting the effective order. For purge_effective_progs(), it could dummy out a slot belonging to a different program and leave the detached program in the array while bpf_prog_put() drops its reference, i.e. a use-after-free. Fix both by replaying compute_effective_progs()'s placement (including the per-cgroup preorder reversal) in a shared effective_prog_pos() helper. Identify the entry by its struct bpf_prog_list pointer rather than by (prog, link) value, so the lookup resolves to exactly the attachment the syscall selected even when the same bpf_prog is attached to several cgroups in the hierarchy.

References

NVD — CVE-2026-72427 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72427
git.kernel.org/stable/c/41b4320b84... WEB
https://git.kernel.org/stable/c/41b4320b84fdafe1ab586b06453d30d50415db59
git.kernel.org/stable/c/525e408c27... WEB
https://git.kernel.org/stable/c/525e408c27ae714e538b8c608c3a974df3ab6c92
git.kernel.org/stable/c/9697db03e0... WEB
https://git.kernel.org/stable/c/9697db03e010391c55ae75192cbdf30c5a72c114
git.kernel.org/stable/c/b584f107ab... WEB
https://git.kernel.org/stable/c/b584f107ab90222bd825dcb4c5977326ff684109
git.kernel.org/stable/c/f08aaee315... WEB
https://git.kernel.org/stable/c/f08aaee3152d0dfc578b3f2586932d82062701dd

Frequently Asked Questions

What is CVE-2026-72427?
CVE-2026-72427 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-72427?
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-72427?
CVE-2026-72427 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-72427?
CVE-2026-72427 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72427?
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-6pxh-c54r-cxc3",
  "modified" : "2026-08-17T06:33:29Z",
  "published" : "2026-08-15T06:32:24Z",
  "aliases" : [ "CVE-2026-72427" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix effective prog array index with BPF_F_PREORDER\n\nreplace_effective_prog() and purge_effective_progs() located the slot in\nthe effective array by walking the program hlist and counting entries\nlinearly. That count does not match the array layout: compute_effective_\nprogs() places BPF_F_PREORDER programs at the front (ancestor cgroup\nfirst, attach order within a cgroup) and the rest after them (descendant\ncgroup first). So when a preorder program is present, the linear hlist\nposition no longer equals the program's index in the effective array.\n\nFor replace_effective_prog() (bpf_link_update()) this overwrote the\nwrong slot, corrupting the effective order. For purge_effective_progs(),\nit could dummy out a slot belonging to a different program and leave the\ndetached program in the array while bpf_prog_put() drops its reference,\ni.e. a use-after-free.\n\nFix both by replaying compute_effective_progs()'s placement (including\nthe per-cgroup preorder reversal) in a shared effective_prog_pos()\nhelper. Identify the entry by its struct bpf_prog_list pointer rather\nthan by (prog, link) value, so the lookup resolves to exactly the\nattachment the syscall selected even when the same bpf_prog is attached\nto several cgroups in the hierarchy.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72427"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/41b4320b84fdafe1ab586b06453d30d50415db59"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/525e408c27ae714e538b8c608c3a974df3ab6c92"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9697db03e010391c55ae75192cbdf30c5a72c114"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b584f107ab90222bd825dcb4c5977326ff684109"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f08aaee3152d0dfc578b3f2586932d82062701dd"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:16Z"
  }
}