CVE-2026-90250: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-90250 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-90250 at a Glance
How to Fix CVE-2026-90250
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-90250, 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-90250?
Which Software versions are affected?
What version fixes CVE-2026-90250?
What CWE is associated with CVE-2026-90250?
How can I check Maven dependencies for CVE-2026-90250?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-364x-ffh5-8mmx",
"modified" : "2026-09-17T18:31:57Z",
"published" : "2026-09-17T18:31:57Z",
"aliases" : [ "CVE-2026-90250" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf, cgroup: Fix storage null-ptr-deref after replacing prog\n\nSyzkaller reported a storage null-ptr-deref issue after replacing prog.\nThis occurs in the following scenario:\n1. prog A, an empty prog, is attached to a cgrp.\n2. prog B uses BPF_MAP_TYPE_PERCPU_CGROUP_STORAGE and calls the\n bpf_get_local_storage helper.\n3. link_update is called to replace prog A with prog B.\n\nThe reason is that __cgroup_bpf_replace fails to alloc and assign the\nrequired cgrp storage for the incoming replacement prog. Consequently,\nthe new prog inherits an uninit storage, leading to null-ptr-deref panic\nwhen kick the new prog.\n\nFix this by rejecting a link update if new_prog's cgroup storage is\nincompatible with link->prog.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90250"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/12feca126831556dc7fabe5a3ba28fbd328768b6"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/1ab3da12061d7ccb099f7e925fa2d865967a316a"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/3f562c537e9ecf4bc5e206cfffc2cc047f1b7e94"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/a033c950f6731be88a7da98604ed78f302f15b80"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-09-17T17:17:21Z"
}
}