CVE-2026-98049: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-wmcq-6rpv-m375
Share
CVSS 5.5
CWE-681
Published
Advisory Summary

CVE-2026-98049 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (CWE-681: Incorrect Conversion between Numeric Types) affecting Software libraries in the Maven ecosystem. The weakness occurs when when converting from one data type to another, such as long to integer, data can be omitted or translated in a way that produces unexpected values. if the resulting values are used in a sensitive context, then dangerous behaviors may occur.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-98049 at a Glance

CVE Identifier CVE-2026-98049
GHSA Identifier GHSA-wmcq-6rpv-m375
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-681: Incorrect Conversion between Numeric Types
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-98049

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-98049, 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 CWE-681: Incorrect Conversion between Numeric Types, where when converting from one data type to another, such as long to integer, data can be omitted or translated in a way that produces unexpected values. if the resulting values are used in a sensitive context, then dangerous behaviors may occur. 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: zero extend the result of an arena 32-bit cmpxchg bpf_convert_ctx_accesses() rewrites an atomic on an arena pointer from BPF_STX | BPF_ATOMIC to BPF_STX | BPF_PROBE_ATOMIC, and it runs before bpf_opt_subreg_zext_lo32_rnd_hi32(). That pass emits an explicit zero extension for a 32-bit cmpxchg even when bpf_jit_needs_zext() is false. This is done because on some architectures 32-bit cmpxchg requires explicit zero extension for the dst register. E.g. on x86-64 'lock cmpxchg' does not change the %eax if comparison is successful, while BPF semantics declare that each operation on a 32-bit register zero extends it's upper half. is_cmpxchg_insn() matches BPF_MODE == BPF_ATOMIC only, so an arena cmpxchg misses said zero extension adjustment. This patch adjusts is_cmpxchg_insn() to match BPF_PROBE_ATOMIC alongside BPF_ATOMIC.

References

NVD — CVE-2026-98049 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-98049
git.kernel.org/stable/c/1c1b476d43... WEB
https://git.kernel.org/stable/c/1c1b476d43a8b6c9bc04600369dd8cc39950d98e
git.kernel.org/stable/c/4814ed6406... WEB
https://git.kernel.org/stable/c/4814ed6406f3493bd554ad046da5f7fc04833571
git.kernel.org/stable/c/6bb6ae5ab1... WEB
https://git.kernel.org/stable/c/6bb6ae5ab1beffda51dabf41612f501d07f10fc6

Frequently Asked Questions

What is CVE-2026-98049?
CVE-2026-98049 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-681: Incorrect Conversion between Numeric Types.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-98049?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-98049?
CVE-2026-98049 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-98049?
CVE-2026-98049 is classified under CWE-681: Incorrect Conversion between Numeric Types (When converting from one data type to another, such as long to integer, data can be omitted or translated in a way that produces unexpected values. If the resulting values are used in a sensitive context, then dangerous behaviors may occur.).
How can I check Maven dependencies for CVE-2026-98049?
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
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wmcq-6rpv-m375",
  "modified" : "2026-10-15T12:30:54Z",
  "published" : "2026-09-25T12:31:34Z",
  "aliases" : [ "CVE-2026-98049" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: zero extend the result of an arena 32-bit cmpxchg\n\nbpf_convert_ctx_accesses() rewrites an atomic on an arena pointer from\nBPF_STX | BPF_ATOMIC to BPF_STX | BPF_PROBE_ATOMIC, and it runs before\nbpf_opt_subreg_zext_lo32_rnd_hi32().\n\nThat pass emits an explicit zero extension for a 32-bit cmpxchg even\nwhen bpf_jit_needs_zext() is false. This is done because on some\narchitectures 32-bit cmpxchg requires explicit zero extension for the\ndst register. E.g. on x86-64 'lock cmpxchg' does not change the %eax\nif comparison is successful, while BPF semantics declare that each\noperation on a 32-bit register zero extends it's upper half.\n\nis_cmpxchg_insn() matches BPF_MODE == BPF_ATOMIC only, so an arena\ncmpxchg misses said zero extension adjustment. This patch adjusts\nis_cmpxchg_insn() to match BPF_PROBE_ATOMIC alongside BPF_ATOMIC.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98049"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1c1b476d43a8b6c9bc04600369dd8cc39950d98e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4814ed6406f3493bd554ad046da5f7fc04833571"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6bb6ae5ab1beffda51dabf41612f501d07f10fc6"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-681" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-25T11:17:33Z"
  }
}