CVE-2026-72155: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-4g3m-gr2j-r4mp
Share
Published
Advisory Summary

CVE-2026-72155 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-72155 at a Glance

CVE Identifier CVE-2026-72155
GHSA Identifier GHSA-4g3m-gr2j-r4mp
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-72155

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-72155, 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

In the Linux kernel, the following vulnerability has been resolved: mtd: spi-nor: swp: Improve locking user experience In the case of the first block being locked (or the few first blocks), if the user want to fully unlock the device it has two possibilities: - either it asks to unlock the entire device, and this works; - or it asks to unlock just the block(s) that are currently locked, which fails. It fails because the conditions "can_be_top" and "can_be_bottom" are true. Indeed, in this case, we unlock everything, so the TB bit does not matter. However in the current implementation, use_top would be true (as this is the favourite option) and lock_len, which in practice should be reduced down to 0, is set to "nor->params->size - (ofs + len)" which is a positive number. This is wrong. An easy way is to simply add an extra condition. In the unlock() path, if we can achieve the same result from both sides, it means we unlock everything and lock_len must simply be 0. A comment is added to clarify that logic.

References

NVD — CVE-2026-72155 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72155
git.kernel.org/stable/c/12d4d69221... WEB
https://git.kernel.org/stable/c/12d4d69221159e6d0e72400ec81195d691169b53
git.kernel.org/stable/c/23c285be8f... WEB
https://git.kernel.org/stable/c/23c285be8f6fcde9088fe12bb69c701d46696be1
git.kernel.org/stable/c/6110ab5ffd... WEB
https://git.kernel.org/stable/c/6110ab5ffd84e8daa654652446a03ce2f77580a7
git.kernel.org/stable/c/9a0d8dec3d... WEB
https://git.kernel.org/stable/c/9a0d8dec3d11ca95d67537ea8fa6ee2730a5038a
git.kernel.org/stable/c/a6fd2145c7... WEB
https://git.kernel.org/stable/c/a6fd2145c73b80bb6a5eed7355a4f63597d712d9
git.kernel.org/stable/c/c0806df5cf... WEB
https://git.kernel.org/stable/c/c0806df5cf806545160f3fdac3c888926ceac557
git.kernel.org/stable/c/dc341272cf... WEB
https://git.kernel.org/stable/c/dc341272cf8e15a2c511db3c4df5dab8adf70ad0
git.kernel.org/stable/c/e1d456b26b... WEB
https://git.kernel.org/stable/c/e1d456b26bf23e30db305a6184e8abd9ab68bbf2

Frequently Asked Questions

What is CVE-2026-72155?
CVE-2026-72155 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-72155?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-72155?
CVE-2026-72155 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72155?
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-4g3m-gr2j-r4mp",
  "modified" : "2026-08-23T15:33:00Z",
  "published" : "2026-08-15T06:32:14Z",
  "aliases" : [ "CVE-2026-72155" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmtd: spi-nor: swp: Improve locking user experience\n\nIn the case of the first block being locked (or the few first blocks),\nif the user want to fully unlock the device it has two possibilities:\n- either it asks to unlock the entire device, and this works;\n- or it asks to unlock just the block(s) that are currently locked,\n  which fails.\n\nIt fails because the conditions \"can_be_top\" and \"can_be_bottom\" are\ntrue. Indeed, in this case, we unlock everything, so the TB bit does not\nmatter. However in the current implementation, use_top would be true (as\nthis is the favourite option) and lock_len, which in practice should be\nreduced down to 0, is set to \"nor->params->size - (ofs + len)\" which is\na positive number. This is wrong.\n\nAn easy way is to simply add an extra condition. In the unlock() path,\nif we can achieve the same result from both sides, it means we unlock\neverything and lock_len must simply be 0. A comment is added to clarify\nthat logic.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72155"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/12d4d69221159e6d0e72400ec81195d691169b53"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/23c285be8f6fcde9088fe12bb69c701d46696be1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6110ab5ffd84e8daa654652446a03ce2f77580a7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9a0d8dec3d11ca95d67537ea8fa6ee2730a5038a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a6fd2145c73b80bb6a5eed7355a4f63597d712d9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c0806df5cf806545160f3fdac3c888926ceac557"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/dc341272cf8e15a2c511db3c4df5dab8adf70ad0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e1d456b26bf23e30db305a6184e8abd9ab68bbf2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:21:33Z"
  }
}