CVE-2026-98505: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-98505 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-98505 at a Glance
How to Fix CVE-2026-98505
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-98505, 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-98505?
Which Software versions are affected?
What version fixes CVE-2026-98505?
What CWE is associated with CVE-2026-98505?
How can I check Maven dependencies for CVE-2026-98505?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-mr9h-5fpp-c352",
"modified" : "2026-10-18T18:31:52Z",
"published" : "2026-10-18T18:31:51Z",
"aliases" : [ "CVE-2026-98505" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/vaddr: avoid hw-driven pte updates during damon_hugetlb_mkold()\n\ndamon_hugetlb_mkold() reads the page table entry into a local variable,\nunsets the accessed bit in the variable, and updates the page table entry\nwith the updated variable value. If hardware updates the same page table\nentry in parallel, the hw updates could be lost. For example,\nhardware-updated dirty bits might be lost.\n\nAvoid the parallel updates by clearing the page table entry when reading\nit together, using huge_ptep_get_and_clear(). If a parallel write to the\nmemory is made after the clearing, the hw will see the page table entry is\ncleared, trigger page fault and wait until it is handled. The page fault\nhandling will wait for damon_hugetlb_mkold() due to the page table lock.\n\nBecause hugetlbfs is an in-memory file system and hugetlb pages cannot be\nreclaimed, no critical issue is expected to my best knowledge. But\ndefinitely this is a nasty bug that should be fixed sooner rather than\nlater.\n\nThe issue was discovered [1] by Sashiko.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-98505"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/00457981327c80bcc56e07d4714fe189337a19fa"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/39c0ceedd54557bdc1542de08d22b2ed33e534e4"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/6e74ffc9ecf6ec24eee117150da78a1102be74c5"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/e59cb7eda7c06334a0faf5aa44adb6acf2a1287a"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-10-18T16:17:01Z"
}
}