CVE-2026-90070: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-q7v7-xw33-v766
Published
Advisory Summary

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

CVE Identifier CVE-2026-90070
GHSA Identifier GHSA-q7v7-xw33-v766
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-90070

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-90070, 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: st33zp24: Return zero on status read failure st33zp24_status() ignores the result of the transport read and returns data even when no byte was received. The I2C transport, for example, skips i2c_master_recv() when the register-select write is short or fails, leaving data uninitialized. The resulting stack value can be interpreted as TPM_STS flags and let status checks complete spuriously. The status callback cannot propagate a transport error. Return zero unless recv() reports exactly one byte. With no status bits set, callers retry or take their existing timeout or error path instead of acting on an invalid status value. This issue was found by a static analysis checker and confirmed by manual source review.

References

Frequently Asked Questions

What is CVE-2026-90070?
CVE-2026-90070 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-90070?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90070?
CVE-2026-90070 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90070?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-q7v7-xw33-v766",
  "modified" : "2026-09-17T18:31:49Z",
  "published" : "2026-09-17T18:31:49Z",
  "aliases" : [ "CVE-2026-90070" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ntpm: st33zp24: Return zero on status read failure\n\nst33zp24_status() ignores the result of the transport read and returns\ndata even when no byte was received. The I2C transport, for example,\nskips i2c_master_recv() when the register-select write is short or fails,\nleaving data uninitialized. The resulting stack value can be interpreted\nas TPM_STS flags and let status checks complete spuriously.\n\nThe status callback cannot propagate a transport error. Return zero\nunless recv() reports exactly one byte. With no status bits set, callers\nretry or take their existing timeout or error path instead of acting on\nan invalid status value.\n\nThis issue was found by a static analysis checker and confirmed by manual\nsource review.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90070"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/14feaa498c20c1b7ddefe27de5329aaff822cc0d"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1bfd5c54e40704ce93d128a25de3d8dd772bf183"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/38c26fe4522963a91d4fb02c844d8faa740fe9d1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4973e8386257eed10e5433a94a53bcc6ec37d2a1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8b92687708f5ef980de01c2042dbd76d11f78547"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/981307e2e8a930da492c2bcf763865c47c2a5165"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d732cfc4befe28f02ec82ed5fd2bc2a21fbabd42"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e6d7d9b665419cda3e9f91030d81c9f8ba71e51d"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:16:55Z"
  }
}