CVE-2026-72103: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-mq86-3x2m-mwpc
Share
CVSS 7.3
CWE-200
Published
Advisory Summary

CVE-2026-72103 is a HIGH (CVSS 7.3) security vulnerability vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-72103 at a Glance

CVE Identifier CVE-2026-72103
GHSA Identifier GHSA-mq86-3x2m-mwpc
Severity HIGH
CVSS v3.1 Base Score 7.3
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.3

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:H/A:L).

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 High (I:H)
Availability Low (A:L)

How to Fix CVE-2026-72103

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-72103, 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-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. 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: dm: avoid leaking the caller's thread keyring via the table device file The refactoring in commit a28d893eb327 ("md: port block device access to file") accidentally causes the caller's thread keyring to be kept alive long beyond the caller's lifetime. As a result, "cryptsetup luksSuspend" silently fails to wipe the LUKS volume key from memory. In detail: "cryptsetup luksOpen" uses its supposedly ephemeral thread keyring to pass the volume key to the kernel. dm-crypt's crypt_set_keyring_key() copies the key material into its own crypt_config structure and then drops its own reference to the key in the keyring with key_put(). With this fix, restoring pre-v6.9 behavior, the copy in the thread keyring is then promptly garbage collected, such that exactly one copy of the volume key remains. This single copy is correctly wiped from memory on "cryptsetup luksSuspend". Without this fix, the thread keyring and the volume key in it remains. This second copy is only freed on "luksClose". "luksSuspend" neither knows about this copy nor has any way to remove it, so the key remains recoverable from RAM after a suspend that is documented to have wiped it. This fix should not introduce new security problems, as the code is anyway gated by CAP_SYS_ADMIN. The device-mapper core, not the calling task, is the legitimate owner of this long-lived file.

References

NVD — CVE-2026-72103 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72103
git.kernel.org/stable/c/8ced1d242c... WEB
https://git.kernel.org/stable/c/8ced1d242c34e342defcccdb00663354f212aae6
git.kernel.org/stable/c/981ccd97f7... WEB
https://git.kernel.org/stable/c/981ccd97f7153d310dfa92a534525bbaf46752c2
git.kernel.org/stable/c/d3eb8451d5... WEB
https://git.kernel.org/stable/c/d3eb8451d529ea452740d1a2bc395a1d20c48133
git.kernel.org/stable/c/f00105be6a... WEB
https://git.kernel.org/stable/c/f00105be6a593920e9bc7949a069d4a116888851

Frequently Asked Questions

What is CVE-2026-72103?
CVE-2026-72103 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-72103?
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-72103?
CVE-2026-72103 has a CVSS v3.1 base score of 7.3 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L.
What CWE is associated with CVE-2026-72103?
CVE-2026-72103 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check Maven dependencies for CVE-2026-72103?
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-mq86-3x2m-mwpc",
  "modified" : "2026-08-17T06:33:09Z",
  "published" : "2026-08-15T06:32:12Z",
  "aliases" : [ "CVE-2026-72103" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndm: avoid leaking the caller's thread keyring via the table device file\n\nThe refactoring in commit a28d893eb327 (\"md: port block device access to file\")\naccidentally causes the caller's thread keyring to be kept alive long\nbeyond the caller's lifetime.\n\nAs a result, \"cryptsetup luksSuspend\" silently fails to wipe the\nLUKS volume key from memory.\n\nIn detail: \"cryptsetup luksOpen\" uses its supposedly ephemeral thread\nkeyring to pass the volume key to the kernel. dm-crypt's\ncrypt_set_keyring_key() copies the key material into its own\ncrypt_config structure and then drops its own reference to the key in\nthe keyring with key_put().\n\nWith this fix, restoring pre-v6.9 behavior, the copy in the thread\nkeyring is then promptly garbage collected, such that exactly one copy\nof the volume key remains. This single copy is correctly wiped from\nmemory on \"cryptsetup luksSuspend\".\n\nWithout this fix, the thread keyring and the volume key in it remains.\nThis second copy is only freed on \"luksClose\". \"luksSuspend\" neither\nknows about this copy nor has any way to remove it, so the key remains\nrecoverable from RAM after a suspend that is documented to have wiped it.\n\nThis fix should not introduce new security problems, as the code is\nanyway gated by CAP_SYS_ADMIN. The device-mapper core, not the calling\ntask, is the legitimate owner of this long-lived file.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72103"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8ced1d242c34e342defcccdb00663354f212aae6"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/981ccd97f7153d310dfa92a534525bbaf46752c2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d3eb8451d529ea452740d1a2bc395a1d20c48133"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f00105be6a593920e9bc7949a069d4a116888851"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:21:24Z"
  }
}