CVE-2026-72135: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-mgw8-pg67-5pw5
Share
CVSS 7.8
Published
Advisory Summary

CVE-2026-72135 is a HIGH (CVSS 7.8) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-72135 at a Glance

CVE Identifier CVE-2026-72135
GHSA Identifier GHSA-mgw8-pg67-5pw5
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

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

How to Fix CVE-2026-72135

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-72135, 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: tpm: Make the TPM character devices non-seekable The TPM character devices expose a sequential command/response interface, but their open handlers leave FMODE_PREAD and FMODE_PWRITE enabled. After a command leaves a response pending, pread(fd, buf, 16, 0x1400) passes 0x1400 as *off to tpm_common_read(). The transfer length is bounded by response_length, but the offset is used unchecked when forming data_buffer + *off. A sufficiently large offset therefore causes an out-of-bounds heap read through copy_to_user() and, if the copy succeeds, an out-of-bounds zero-write through the following memset(). Positional I/O does not provide coherent semantics for this interface. An arbitrary pread offset cannot represent how much of a response has been consumed sequentially. The write callback always stores a command at the start of data_buffer, while pwrite() does not update file->f_pos and can leave the sequential read cursor stale. Call nonseekable_open() from both open handlers. This removes FMODE_PREAD and FMODE_PWRITE, causing positional reads and writes to fail with -ESPIPE before reaching the TPM callbacks, and explicitly marks the files non-seekable. Normal read() and write() continue to use the existing sequential f_pos cursor, leaving the response state machine unchanged. Tested on Linux 6.12 with KASAN and a swtpm TPM2 device: - sequential partial reads returned the complete response - pread() and preadv() with offset 0x1400 returned -ESPIPE - pwrite() and pwritev() with offset zero returned -ESPIPE - the pending response remained intact after the rejected operations - a subsequent normal command/response cycle completed normally - no KASAN report was produced.

References

NVD — CVE-2026-72135 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-72135
git.kernel.org/stable/c/21a13f9329... WEB
https://git.kernel.org/stable/c/21a13f932972bc9836f58c44fcd47c62abdecd95
git.kernel.org/stable/c/232dcf908e... WEB
https://git.kernel.org/stable/c/232dcf908eb7eb9d8046a9597975caf44270966e
git.kernel.org/stable/c/947b773caa... WEB
https://git.kernel.org/stable/c/947b773caaa548672184df025271b29bdc80b0f1
git.kernel.org/stable/c/9c513dabd4... WEB
https://git.kernel.org/stable/c/9c513dabd4540f811585a2087f23069767a284da
git.kernel.org/stable/c/ada4b9a508... WEB
https://git.kernel.org/stable/c/ada4b9a5087ea7f30dd8e4c6411a4fb6547eb1ed
git.kernel.org/stable/c/dda695fab5... WEB
https://git.kernel.org/stable/c/dda695fab5e21f923d29e8cb01df256468ddfbd1
git.kernel.org/stable/c/ed0ffc2c01... WEB
https://git.kernel.org/stable/c/ed0ffc2c016629e40ba041ed0424a772d8b02e2c
git.kernel.org/stable/c/f20d61c22b... WEB
https://git.kernel.org/stable/c/f20d61c22bcaf172d6790b6500e3838e532e71c8

Frequently Asked Questions

What is CVE-2026-72135?
CVE-2026-72135 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-72135?
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-72135?
CVE-2026-72135 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-72135?
CVE-2026-72135 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72135?
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-mgw8-pg67-5pw5",
  "modified" : "2026-08-17T06:33:12Z",
  "published" : "2026-08-15T06:32:13Z",
  "aliases" : [ "CVE-2026-72135" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ntpm: Make the TPM character devices non-seekable\n\nThe TPM character devices expose a sequential command/response\ninterface, but their open handlers leave FMODE_PREAD and FMODE_PWRITE\nenabled.\n\nAfter a command leaves a response pending, pread(fd, buf, 16, 0x1400)\npasses 0x1400 as *off to tpm_common_read(). The transfer length is\nbounded by response_length, but the offset is used unchecked when\nforming data_buffer + *off. A sufficiently large offset therefore causes\nan out-of-bounds heap read through copy_to_user() and, if the copy\nsucceeds, an out-of-bounds zero-write through the following memset().\n\nPositional I/O does not provide coherent semantics for this interface.\nAn arbitrary pread offset cannot represent how much of a response has\nbeen consumed sequentially. The write callback always stores a command\nat the start of data_buffer, while pwrite() does not update file->f_pos\nand can leave the sequential read cursor stale.\n\nCall nonseekable_open() from both open handlers. This removes\nFMODE_PREAD and FMODE_PWRITE, causing positional reads and writes to\nfail with -ESPIPE before reaching the TPM callbacks, and explicitly\nmarks the files non-seekable. Normal read() and write() continue to use\nthe existing sequential f_pos cursor, leaving the response state machine\nunchanged.\n\nTested on Linux 6.12 with KASAN and a swtpm TPM2 device:\n\n - sequential partial reads returned the complete response\n - pread() and preadv() with offset 0x1400 returned -ESPIPE\n - pwrite() and pwritev() with offset zero returned -ESPIPE\n - the pending response remained intact after the rejected operations\n - a subsequent normal command/response cycle completed normally\n - no KASAN report was produced.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72135"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/21a13f932972bc9836f58c44fcd47c62abdecd95"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/232dcf908eb7eb9d8046a9597975caf44270966e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/947b773caaa548672184df025271b29bdc80b0f1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9c513dabd4540f811585a2087f23069767a284da"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ada4b9a5087ea7f30dd8e4c6411a4fb6547eb1ed"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/dda695fab5e21f923d29e8cb01df256468ddfbd1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ed0ffc2c016629e40ba041ed0424a772d8b02e2c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f20d61c22bcaf172d6790b6500e3838e532e71c8"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:21:30Z"
  }
}