CVE-2026-46020: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-qpc9-3gvw-7vfq
Share
CVSS 7.1
CWE-125
Published
Advisory Summary

CVE-2026-46020 is a HIGH (CVSS 7.1) security vulnerability vulnerability (CWE-125: Out-of-bounds Read) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product reads data past the end, or before the beginning, of the intended buffer.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-46020 at a Glance

CVE Identifier CVE-2026-46020
GHSA Identifier GHSA-qpc9-3gvw-7vfq
Severity HIGH
CVSS v3.1 Base Score 7.1
CWE Classification CWE-125: Out-of-bounds Read
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.1

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:H/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 High (C:H)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-46020

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-46020, 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-125: Out-of-bounds Read, where the product reads data past the end, or before the beginning, of the intended buffer. 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: mm/damon/core: validate damos_quota_goal->nid for node_mem_{used,free}_bp Patch series "mm/damon/core: validate damos_quota_goal->nid". node_mem[cg]_{used,free}_bp DAMOS quota goals receive the node id. The node id is used for si_meminfo_node() and NODE_DATA() without proper validation. As a result, privileged users can trigger an out of bounds memory access using DAMON_SYSFS. Fix the issues. The issue was originally reported [1] with a fix by another author. The original author announced [2] that they will stop working including the fix that was still in the review stage. Hence I'm restarting this. This patch (of 2): Users can set damos_quota_goal->nid with arbitrary value for node_mem_{used,free}_bp. But DAMON core is using those for si_meminfo_node() without the validation of the value. This can result in out of bounds memory access. The issue can actually triggered using DAMON user-space tool (damo), like below. $ sudo ./damo start --damos_action stat \ --damos_quota_goal node_mem_used_bp 50% -1 \ --damos_quota_interval 1s $ sudo dmesg [...] [ 65.565986] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000098 Fix this issue by adding the validation of the given node. If an invalid node id is given, it returns 0% for used memory ratio, and 100% for free memory ratio.

References

NVD — CVE-2026-46020 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-46020
git.kernel.org/stable/c/40250b2dde... WEB
https://git.kernel.org/stable/c/40250b2dded0604a112be605f3828700d80ad7c2
git.kernel.org/stable/c/b09958e235... WEB
https://git.kernel.org/stable/c/b09958e235f2b9cd3898b85a8529172afa80d212
git.kernel.org/stable/c/bcad740787... WEB
https://git.kernel.org/stable/c/bcad74078708f2330a45b55358ebc38f8f4b1127

Frequently Asked Questions

What is CVE-2026-46020?
CVE-2026-46020 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-125: Out-of-bounds Read.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-46020?
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-46020?
CVE-2026-46020 has a CVSS v3.1 base score of 7.1 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H.
What CWE is associated with CVE-2026-46020?
CVE-2026-46020 is classified under CWE-125: Out-of-bounds Read (The product reads data past the end, or before the beginning, of the intended buffer.).
How can I check Maven dependencies for CVE-2026-46020?
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-qpc9-3gvw-7vfq",
  "modified" : "2026-06-16T18:32:28Z",
  "published" : "2026-05-27T15:33:20Z",
  "aliases" : [ "CVE-2026-46020" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/core: validate damos_quota_goal->nid for node_mem_{used,free}_bp\n\nPatch series \"mm/damon/core: validate damos_quota_goal->nid\".\n\nnode_mem[cg]_{used,free}_bp DAMOS quota goals receive the node id.  The\nnode id is used for si_meminfo_node() and NODE_DATA() without proper\nvalidation.  As a result, privileged users can trigger an out of bounds\nmemory access using DAMON_SYSFS.  Fix the issues.\n\nThe issue was originally reported [1] with a fix by another author.  The\noriginal author announced [2] that they will stop working including the\nfix that was still in the review stage.  Hence I'm restarting this.\n\n\nThis patch (of 2):\n\nUsers can set damos_quota_goal->nid with arbitrary value for\nnode_mem_{used,free}_bp.  But DAMON core is using those for\nsi_meminfo_node() without the validation of the value.  This can result in\nout of bounds memory access.  The issue can actually triggered using DAMON\nuser-space tool (damo), like below.\n\n    $ sudo ./damo start --damos_action stat \\\n    \t--damos_quota_goal node_mem_used_bp 50% -1 \\\n    \t--damos_quota_interval 1s\n    $ sudo dmesg\n    [...]\n    [   65.565986] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000098\n\nFix this issue by adding the validation of the given node.  If an invalid\nnode id is given, it returns 0% for used memory ratio, and 100% for free\nmemory ratio.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-46020"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/40250b2dded0604a112be605f3828700d80ad7c2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b09958e235f2b9cd3898b85a8529172afa80d212"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/bcad74078708f2330a45b55358ebc38f8f4b1127"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-125" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-05-27T14:17:20Z"
  }
}