CVE-2026-98627: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98627 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-98627 at a Glance
How to Fix CVE-2026-98627
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-98627, 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-98627?
Which Software versions are affected?
What version fixes CVE-2026-98627?
What CWE is associated with CVE-2026-98627?
How can I check Maven dependencies for CVE-2026-98627?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-p3gw-45vq-6cwq",
"modified" : "2026-10-18T18:31:56Z",
"published" : "2026-10-18T18:31:56Z",
"aliases" : [ "CVE-2026-98627" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Preserve packet pointer class displacement in regsafe()\n\nregsafe() maps packet pointer IDs between states and checks that each\ncurrent register range is a subset of the corresponding explored\nregister range. It does not, however, preserve the displacement between\nregisters that share a packet pointer ID.\n\nThis is unsound because packet range is shared by ID. A bounds check on\none class member updates every member, and a later access can consume the\nrange through another member. Commit 022ac0750883 (\"bpf: use reg->var_off\ninstead of reg->off for pointers\") folded the fixed pointer offset into\nr64 and removed the old off equality check, so two individually narrower\nregisters can prune even when their displacement has changed. The\nexplored path can then license an out-of-bounds packet access on the\npruned path.\n\nRequire matching range bases for packet pointers with an ID. Together\nwith the existing ID mapping, this preserves the displacement between\nmembers of each packet-pointer class without adding per-ID state.\nPacket pointers without an ID remain unaffected.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98627"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/091b40845bd3cf96791171ca95113e9184ccb596"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/fd16449a9b3b31a8f18944c2f0e29e4e218ca2cf"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-18T16:17:15Z"
}
}