CVE-2026-98799: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98799 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-98799 at a Glance
How to Fix CVE-2026-98799
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-98799, 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-98799?
Which Software versions are affected?
What version fixes CVE-2026-98799?
What CWE is associated with CVE-2026-98799?
How can I check Maven dependencies for CVE-2026-98799?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-h23c-62pq-37fc",
"modified" : "2026-10-18T18:32:04Z",
"published" : "2026-10-18T18:32:04Z",
"aliases" : [ "CVE-2026-98799" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Skip detached progs in trampoline images that are still in use\n\nbpf_tramp_image_put() makes sure a trampoline image is not freed while\na task may still be running in it, but nothing similar is done for the\nprogs called by that image. Detach drops the last prog reference right\naway and the prog is freed after grace periods, on the basis that a\ntask still in the traced function skips the fexit progs once the nop at\nip_after_call is patched to a jump.\n\nThat leaves out a task sleeping in a sleepable prog that runs before\nthe detached one, which no grace period waits for:\n\n CPU 0 CPU 1\n in image I, sleeping in prog S\n detach P from I's trampoline\n -> new image, bpf_tramp_image_put(I)\n bpf_prog_put(P), last ref\n grace periods, P freed\n back from S\n __bpf_prog_enter(P)\n call P->bpf_func\n\nIf S and P are fexit progs the task is already past the patched jump,\nand fentry only images don't have one. On x86 this is an int3 in\npoisoned bpf_prog_pack memory:\n\n Oops: int3: 0000 [#1] SMP NOPTI\n CPU: 18 UID: 0 PID: 94573 Comm: x169 Not tainted 6.18.44 #1 PREEMPT(lazy)\n RIP: 0010:0xffffffffc0601d8d\n Call Trace:\n <TASK>\n ? bpf_trampoline_6442515411+0x1a4/0x21b\n bpf_lsm_bprm_committed_creds+0x5/0x10\n security_bprm_committed_creds+0x5f/0x70\n begin_new_exec+0x2d6/0x410\n ...\n\nWe hit this in production when progs attached through trampolines got\ndetached while their hooks were busy, and it was independently found\nwith a fuzzer and KASAN.\n\nHave the JITs emit a patchable nop in front of each prog call sequence\nand record it in the image. When a prog is detached, patch its nop to a\njump over the call sequence. Progs that stay attached keep running for\nthe tasks that are in the image, and ip_after_call isn't needed anymore.\n\nThe task can be in any image that isn't freed yet, not only in the\ncurrent one. It sleeps in image I1 that calls S, P and Q, then P is\ndetached and the trampoline moves to image I2, then Q is detached and\nits call is still in I1. So the trampoline keeps a list of its images\nuntil they are freed, and detaching a prog patches its nop in all of\nthem. Images hold a reference on the trampoline for that long.\n\nOn riscv and loongarch a jump of any range takes several instructions,\nand a task preempted in the middle of them could resume into half of the\nnew sequence. The nop is a single instruction there, patched to a near\nbranch through arch_bpf_trampoline_skip().\n\nWith the extra nops, BPF_MAX_TRAMP_LINKS progs no longer fit in a page\non x86 and arm64 (and already didn't on powerpc), so lower the limit\nthere like s390 does.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98799"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/17637e1a581a22466ac3620a91e099683ff9cc6f"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/967566ad325b42150483e81acb09ea9d800c00b8"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-18T16:17:33Z"
}
}