CVE-2026-90042: Software Security Vulnerability Vulnerability

CRITICAL
Advisory Identifier: GHSA-39q8-gjm7-pm22
Share
CVSS 9.8
Published
Advisory Summary

CVE-2026-90042 is a CRITICAL (CVSS 9.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-90042 at a Glance

CVE Identifier CVE-2026-90042
GHSA Identifier GHSA-39q8-gjm7-pm22
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
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-90042

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-90042, 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: ceph: properly decrypt filenames in vmalloc() buffers The fscrypt subsystem uses the scatterlist crypto API, inheriting its requirement that any buffers are in the linear mapping region. However, the messenger client uses kvmalloc() to create buffers for messages, which will occasionally place those buffers in the vmalloc() region when physical memory fragmentation doesn't permit a large enough kmalloc(). The various callers of ceph_fname_to_usr() directly pass (slices of) raw messages from the MDS without considering that the messages may be in vmalloc() buffers, resulting in oopses especially on non-x86 platforms (see 'Closes:' for more details and a reproducer). Make ceph_fname_to_usr() explicitly tolerant of vmalloc()-allocated fname->ctext, fname->name, and/or oname->name buffers, using `tname` (which, when non-null, must be a linear address; when null, is briefly allocated as necessary) as a bounce buffer to avoid passing any inappropriate addresses to fscrypt_fname_disk_to_usr(). Additionally change parse_reply_info_readdir() -- the only function to supply its own `tname` -- to follow the new "tname must never come from vmalloc()" rule by passing NULL when the message is not in the linear region. Though this causes a per-dentry kmalloc()+kfree(), this overhead exists only when processing the minority of messages that spill into vmalloc(). My (crude) testing puts this at only about 1 in 8,000 readdir messages. Still, if the overhead proves unreasonable in the future, it is easy enough to mitigate: a future change could allocate a bounce buffer in parse_reply_info_readdir() and use that as `tname` instead.

References

NVD — CVE-2026-90042 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90042
git.kernel.org/stable/c/110747ff53... WEB
https://git.kernel.org/stable/c/110747ff535e3d98ac17d68dbd056bb6ef000e23
git.kernel.org/stable/c/3b467c6880... WEB
https://git.kernel.org/stable/c/3b467c68803d7c7e82678289e598afd44faa6101
git.kernel.org/stable/c/93729594af... WEB
https://git.kernel.org/stable/c/93729594af506557a86f8b603be7ac5f3370eeca
git.kernel.org/stable/c/e939fc6a7b... WEB
https://git.kernel.org/stable/c/e939fc6a7bd969a58a150b7f188c1047138403e3

Frequently Asked Questions

What is CVE-2026-90042?
CVE-2026-90042 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-90042?
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-90042?
CVE-2026-90042 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-90042?
CVE-2026-90042 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90042?
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-39q8-gjm7-pm22",
  "modified" : "2026-09-21T15:31:43Z",
  "published" : "2026-09-16T12:30:46Z",
  "aliases" : [ "CVE-2026-90042" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nceph: properly decrypt filenames in vmalloc() buffers\n\nThe fscrypt subsystem uses the scatterlist crypto API, inheriting its\nrequirement that any buffers are in the linear mapping region. However,\nthe messenger client uses kvmalloc() to create buffers for messages,\nwhich will occasionally place those buffers in the vmalloc() region when\nphysical memory fragmentation doesn't permit a large enough kmalloc().\nThe various callers of ceph_fname_to_usr() directly pass (slices of) raw\nmessages from the MDS without considering that the messages may be in\nvmalloc() buffers, resulting in oopses especially on non-x86 platforms\n(see 'Closes:' for more details and a reproducer).\n\nMake ceph_fname_to_usr() explicitly tolerant of vmalloc()-allocated\nfname->ctext, fname->name, and/or oname->name buffers, using `tname`\n(which, when non-null, must be a linear address; when null, is briefly\nallocated as necessary) as a bounce buffer to avoid passing any\ninappropriate addresses to fscrypt_fname_disk_to_usr().\n\nAdditionally change parse_reply_info_readdir() -- the only function to\nsupply its own `tname` -- to follow the new \"tname must never come from\nvmalloc()\" rule by passing NULL when the message is not in the linear\nregion. Though this causes a per-dentry kmalloc()+kfree(), this overhead\nexists only when processing the minority of messages that spill into\nvmalloc(). My (crude) testing puts this at only about 1 in 8,000 readdir\nmessages. Still, if the overhead proves unreasonable in the future, it\nis easy enough to mitigate: a future change could allocate a bounce\nbuffer in parse_reply_info_readdir() and use that as `tname` instead.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90042"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/110747ff535e3d98ac17d68dbd056bb6ef000e23"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3b467c68803d7c7e82678289e598afd44faa6101"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/93729594af506557a86f8b603be7ac5f3370eeca"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e939fc6a7bd969a58a150b7f188c1047138403e3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "CRITICAL",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:17:17Z"
  }
}