CVE-2026-45990: Software Security Vulnerability Vulnerability
MODERATECVE-2026-45990 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (CWE-190: Integer Overflow or Wraparound) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. this occurs when an integer value is incremented to a value that is too large to store in the associated representation. when this occurs, the value may become a very small or negative number.. Remediation is available in the latest vendor maintenance releases.
CVE-2026-45990 at a Glance
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).
How to Fix CVE-2026-45990
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:treeHow to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-45990, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:treeAnalyze 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-190: Integer Overflow or Wraparound, where the product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. this occurs when an integer value is incremented to a value that is too large to store in the associated representation. when this occurs, the value may become a very small or negative number. 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-45990?
Which Software versions are affected?
What version fixes CVE-2026-45990?
What is the CVSS score of CVE-2026-45990?
What CWE is associated with CVE-2026-45990?
How can I check Maven dependencies for CVE-2026-45990?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-q4r9-vxp8-26x5",
"modified" : "2026-06-16T15:33:40Z",
"published" : "2026-05-27T15:33:19Z",
"aliases" : [ "CVE-2026-45990" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nslub: fix data loss and overflow in krealloc()\n\nCommit 2cd8231796b5 (\"mm/slub: allow to set node and align in\nk[v]realloc\") introduced the ability to force a reallocation if the\noriginal object does not satisfy new alignment or NUMA node, even when\nthe object is being shrunk.\n\nThis introduced two bugs in the reallocation fallback path:\n\n1. Data loss during NUMA migration: The jump to 'alloc_new' happens\n before 'ks' and 'orig_size' are initialized. As a result, the\n memcpy() in the 'alloc_new' block would copy 0 bytes into the new\n allocation.\n\n2. Buffer overflow during shrinking: When shrinking an object while\n forcing a new alignment, 'new_size' is smaller than the old size.\n However, the memcpy() used the old size ('orig_size ?: ks'), leading\n to an out-of-bounds write.\n\nThe same overflow bug exists in the kvrealloc() fallback path, where the\nold bucket size ksize(p) is copied into the new buffer without being\nbounded by the new size.\n\nA simple reproducer:\n\n\t// e.g. add to lkdtm as KREALLOC_SHRINK_OVERFLOW\n\twhile (1) {\n\t\tvoid *p = kmalloc(128, GFP_KERNEL);\n\t\tp = krealloc_node_align(p, 64, 256, GFP_KERNEL, NUMA_NO_NODE);\n\t\tkfree(p);\n\t}\n\ndemonstrates the issue:\n\n ==================================================================\n BUG: KFENCE: out-of-bounds write in memcpy_orig+0x68/0x130\n\n Out-of-bounds write at 0xffff8883ad757038 (120B right of kfence-#47):\n memcpy_orig+0x68/0x130\n krealloc_node_align_noprof+0x1c8/0x340\n lkdtm_KREALLOC_SHRINK_OVERFLOW+0x8c/0xc0 [lkdtm]\n lkdtm_do_action+0x3a/0x60 [lkdtm]\n ...\n\n kfence-#47: 0xffff8883ad756fc0-0xffff8883ad756fff, size=64, cache=kmalloc-64\n\n allocated by task 316 on cpu 7 at 97.680481s (0.021813s ago):\n krealloc_node_align_noprof+0x19c/0x340\n lkdtm_KREALLOC_SHRINK_OVERFLOW+0x8c/0xc0 [lkdtm]\n lkdtm_do_action+0x3a/0x60 [lkdtm]\n ...\n ==================================================================\n\nFix it by moving the old size calculation to the top of __do_krealloc()\nand bounding all copy lengths by the new allocation size.",
"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-45990"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/082a6d03a2d685a83a332666b500ad3966349588"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/38387ccc0fbe38d14fb4c2ad7ee1d7404e5e59fd"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/550fa6b5aabb096554536ac1e3ec96b76cbb35fd"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-190" ],
"severity" : "MODERATE",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-05-27T14:17:16Z"
}
}