CVE-2026-93235: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-pxxc-gx8x-h7j2
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-93235
GHSA Identifier GHSA-pxxc-gx8x-h7j2
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-93235

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-93235, 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: f2fs: fix to zero post-EOF data when extending file size generic/794 4s ... - output mismatch (see /share/git/fstests/results//generic/794.out.bad) --- tests/generic/794.out 2026-06-12 08:46:32.766426241 +0800 +++ /share/git/fstests/results//generic/794.out.bad 2026-07-05 18:32:55.000000000 +0800 @@ -1,4 +1,16 @@ QA output created by 794 append_write +FAIL: non-zero data in gap [4080,4096) after shutdown+remount +000000 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a >ZZZZZZZZZZZZZZZZ< +* +001000 truncate_up ... (Run 'diff -u /share/git/fstests/tests/generic/794.out /share/git/fstests/results//generic/794.out.bad' to see the entire diff) Ran: generic/794 Failures: generic/794 Failed 1 of 1 tests Steps of generic/794: 1. write 4096 bytes to file w/ 0x5a 2. use fiemap to get PBA of first block in file 3. truncate file to 4080 4. umount; write 4096 bytes to file w/ 0x5a directly via PBA; mount 5. extend filesize via a) append 4096 from offset 4096, or b) truncate 8192, or c) fallocate 4096 from offset 4096 6. verify the gap is zeroed in memory [4080,4096) 7. sync range 4096 from offset 4096; shutdown -f (flush meta before shutdown) 8. umount; mount; verify [4080,4096) is zeroed or not. When extending file size (e.g. via truncate, fallocate, or write) across an unaligned EOF boundary, we need to ensure that post-EOF data in the partial page is zeroed out in pagecache and marked dirty, then writeback the cache to persist zeroed data before committing inode w/ updated i_size. This help to prevent stale disk data beyond the previous EOF from being exposed after remounting or crash recovery. Since f2fs is a LFS filesystem, we only support direct write via PBA in pinfile, and pinfile has section-aligned filesize, so in Android, there should no problem, but for other usage in different environment, let's fix this w/ fsync_mode=strict mount option.

References

NVD — CVE-2026-93235 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93235
git.kernel.org/stable/c/32c7f11a24... WEB
https://git.kernel.org/stable/c/32c7f11a24268ba8d3bb50ea7f54d33f698cd253
git.kernel.org/stable/c/5eced87b7d... WEB
https://git.kernel.org/stable/c/5eced87b7d19dbc76ebdddaf322046f9ac582fcb
git.kernel.org/stable/c/6882d458d2... WEB
https://git.kernel.org/stable/c/6882d458d2e403f6ba7b45542dd31a6b7531eb2e
git.kernel.org/stable/c/91ec55ddc0... WEB
https://git.kernel.org/stable/c/91ec55ddc097ccddd25ffb95a3d079b2ef362372
git.kernel.org/stable/c/c42608c09b... WEB
https://git.kernel.org/stable/c/c42608c09b6b5d5967bf211c255914c068c2cde1

Frequently Asked Questions

What is CVE-2026-93235?
CVE-2026-93235 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-93235?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-93235?
CVE-2026-93235 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93235?
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-pxxc-gx8x-h7j2",
  "modified" : "2026-09-24T18:31:23Z",
  "published" : "2026-09-24T18:31:23Z",
  "aliases" : [ "CVE-2026-93235" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to zero post-EOF data when extending file size\n\ngeneric/794  4s ... - output mismatch (see /share/git/fstests/results//generic/794.out.bad)\n    --- tests/generic/794.out   2026-06-12 08:46:32.766426241 +0800\n    +++ /share/git/fstests/results//generic/794.out.bad 2026-07-05 18:32:55.000000000 +0800\n    @@ -1,4 +1,16 @@\n     QA output created by 794\n     append_write\n    +FAIL: non-zero data in gap [4080,4096) after shutdown+remount\n    +000000 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a  >ZZZZZZZZZZZZZZZZ<\n    +*\n    +001000\n     truncate_up\n    ...\n    (Run 'diff -u /share/git/fstests/tests/generic/794.out /share/git/fstests/results//generic/794.out.bad'  to see the entire diff)\nRan: generic/794\nFailures: generic/794\nFailed 1 of 1 tests\n\nSteps of generic/794:\n1. write 4096 bytes to file w/ 0x5a\n2. use fiemap to get PBA of first block in file\n3. truncate file to 4080\n4. umount; write 4096 bytes to file w/ 0x5a directly via PBA; mount\n5. extend filesize via\n   a) append 4096 from offset 4096, or\n   b) truncate 8192, or\n   c) fallocate 4096 from offset 4096\n6. verify the gap is zeroed in memory [4080,4096)\n7. sync range 4096 from offset 4096; shutdown -f (flush meta before shutdown)\n8. umount; mount; verify [4080,4096) is zeroed or not.\n\nWhen extending file size (e.g. via truncate, fallocate, or write) across an\nunaligned EOF boundary, we need to ensure that post-EOF data in the partial\npage is zeroed out in pagecache and marked dirty, then writeback the cache to\npersist zeroed data before committing inode w/ updated i_size.\n\nThis help to prevent stale disk data beyond the previous EOF from being exposed\nafter remounting or crash recovery.\n\nSince f2fs is a LFS filesystem, we only support direct write via PBA in pinfile,\nand pinfile has section-aligned filesize, so in Android, there should no problem,\nbut for other usage in different environment, let's fix this w/ fsync_mode=strict\nmount option.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93235"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/32c7f11a24268ba8d3bb50ea7f54d33f698cd253"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5eced87b7d19dbc76ebdddaf322046f9ac582fcb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6882d458d2e403f6ba7b45542dd31a6b7531eb2e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/91ec55ddc097ccddd25ffb95a3d079b2ef362372"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c42608c09b6b5d5967bf211c255914c068c2cde1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-24T16:17:19Z"
  }
}