CVE-2026-90272: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-90272 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-90272 at a Glance
How to Fix CVE-2026-90272
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-90272, 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-90272?
Which Software versions are affected?
What version fixes CVE-2026-90272?
What CWE is associated with CVE-2026-90272?
How can I check Maven dependencies for CVE-2026-90272?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-8j89-gr3p-jpp8",
"modified" : "2026-09-17T18:31:58Z",
"published" : "2026-09-17T18:31:58Z",
"aliases" : [ "CVE-2026-90272" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nperf: arm_pmuv3: Zero initialize hw_id branch stack field\n\nPERF_SAMPLE_BRANCH_HW_INDEX is supported by BRBE so hw_id is passed to\nuserspace, but it's never set by the BRBE driver. Zero initialize it as\nit should be according to the docs:\n\n * For the architectures whose raw branch records are\n * already stored in age order, the hw_idx should be 0.\n\nIt's probably too risky to remove PERF_SAMPLE_BRANCH_HW_INDEX from BRBE\nnow in case anyone is setting it and reading the value, but zero\ninitializing the whole struct also protects against the same issue with\nnew fields that are added in the future.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90272"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/57b72442c1672963fd51ab441ca1b71f6dc79b66"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/7c3b63386c27bed8d59a4b4c283d02860420eb0a"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/988e11b69ef9d4034e19c64407030fa948580c3d"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-17T17:17:23Z"
}
}