CVE-2026-72127: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-72127 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.
CVE-2026-72127 at a Glance
How to Fix CVE-2026-72127
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.
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-72127, 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
References
Frequently Asked Questions
What is CVE-2026-72127?
Which Software versions are affected?
What version fixes CVE-2026-72127?
What CWE is associated with CVE-2026-72127?
How can I check Maven dependencies for CVE-2026-72127?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-hx9w-mw8p-76q2",
"modified" : "2026-08-15T06:32:13Z",
"published" : "2026-08-15T06:32:13Z",
"aliases" : [ "CVE-2026-72127" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnetdev-genl: report NAPI thread PID in the caller's pid namespace\n\nnetdev_nl_napi_fill_one() reports the NAPI kthread PID in NETDEV_A_NAPI_PID\nusing task_pid_nr(), which returns the PID in the initial pid namespace.\n\nNETDEV_CMD_NAPI_GET does not have GENL_ADMIN_PERM and the netdev genl family\nis netnsok, so a caller in a child pid namespace can issue it. That caller\nthen sees the kthread's global PID, even though the kthread is not visible\nin its pid namespace, where the value should be 0.\n\nTranslate the PID through the caller's pid namespace, the same way commit\n3799c2570982 (\"io_uring/fdinfo: translate SqThread PID through caller's\npid_ns\") did for the io_uring SQPOLL thread. The doit and dumpit paths both\nrun synchronously in the caller's context, so task_active_pid_ns(current) is\nthe caller's pid namespace.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72127"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/1f24c0d01db214c9e661915e9972404c96ca73c0"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/5e4c8e08ce95730c87d6ada0bdbe1131a3c06393"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/fb18095389fe81f140d39585a2624aca9d42227e"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/fd750b694f1f9e1ecb8ca19314e4e21edbb15f42"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-15T06:21:30Z"
}
}