CVE-2026-98589: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-2cxv-r576-wfcv
Published
Advisory Summary

CVE-2026-98589 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-98589 at a Glance

CVE Identifier CVE-2026-98589
GHSA Identifier GHSA-2cxv-r576-wfcv
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-98589

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-98589, 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: Reject pkt arguments in mutating subprogs The verifier tracks changes in how PTR_TO_PACKET registers' bounds are modified across subprog boundaries. PTR_TO_PACKET registers are actually passed as PTR_TO_MEM, which is assumed valid for the entire call. This is not the case with packet memory, where a pskb_* call may invalidate its memory region. Reject BPF code that passes PTR_TO_PACKET pointers to subprogs that may mutate a packet. We cannot pass the pointer as a true PTR_TO_PACKET because we would also need to somehow pass the PTR_TO_PACKET_META or PTR_TO_PACKET_END to the subprog. Since we cannot avoid representing the pointer in the subprog as PTR_TO_MEM, only permit it if the subprog is guaranteed not to mutate the packet.

References

Frequently Asked Questions

What is CVE-2026-98589?
CVE-2026-98589 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-98589?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-98589?
CVE-2026-98589 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-98589?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2cxv-r576-wfcv",
  "modified" : "2026-10-18T18:31:55Z",
  "published" : "2026-10-18T18:31:55Z",
  "aliases" : [ "CVE-2026-98589" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject pkt arguments in mutating subprogs\n\nThe verifier tracks changes in how PTR_TO_PACKET registers'\nbounds are modified across subprog boundaries. PTR_TO_PACKET\nregisters are actually passed as PTR_TO_MEM, which is assumed\nvalid for the entire call. This is not the case with packet memory,\nwhere a pskb_* call may invalidate its memory region.\n\nReject BPF code that passes PTR_TO_PACKET pointers to subprogs that\nmay mutate a packet. We cannot pass the pointer as a true PTR_TO_PACKET\nbecause we would also need to somehow pass the PTR_TO_PACKET_META\nor PTR_TO_PACKET_END to the subprog. Since we cannot avoid representing\nthe pointer in the subprog as PTR_TO_MEM, only permit it if the\nsubprog is guaranteed not to mutate the packet.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98589"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0b6b2bb9b90ad1e2d94d18f626258a1dbbdee0ea"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a6c1edfbe240e4377038a0e1d233ad81fde9a21b"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-10-18T16:17:11Z"
  }
}