CVE-2026-90199: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-6r4v-32r5-fpv2
Share
CVSS 7.8
Published
Advisory Summary

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

CVE Identifier CVE-2026-90199
GHSA Identifier GHSA-6r4v-32r5-fpv2
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:N/UI:R/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-90199

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-90199, 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: fs/ntfs3: reject out-of-range evcn in mi_enum_attr() In mi_enum_attr(), the start/end VCN validation for non-resident attributes is: if (svcn > evcn + 1) goto out; When evcn is U64_MAX the "evcn + 1" expression wraps to 0 and any svcn passes the check. For evcn values close to U64_MAX (but not equal to it) the right-hand side is still a meaningless near-wrap upper bound, so a malformed on-disk attribute with svcn == 0 and evcn near U64_MAX can pass mi_enum_attr() unrejected. VCN (virtual cluster number) is a cluster index, so any valid evcn is bounded by the volume's total cluster count, which ntfs3 holds in sbi->used.bitmap.nbits (set up in ntfs_init_from_boot() before any caller of mi_enum_attr() runs). Reject evcn values that fall outside this range. However, an empty non-resident attribute (no allocated clusters) is legitimately encoded with svcn == 0 and evcn == -1 (U64_MAX), e.g. via attr->nres.evcn = cpu_to_le64((u64)vcn - 1) with vcn == 0. That sentinel must keep passing, so exclude evcn == U64_MAX from the range check. The existing "svcn > evcn + 1" test still tolerates the sentinel ("0 > 0" is false) and continues to require svcn == 0 for it, while the range check rejects every other out-of-range evcn and thereby also defuses the "evcn + 1" wraparound. svcn does not need its own bound: once evcn < nbits, "svcn > evcn + 1" implies svcn <= nbits. [almaz.alexandrovich@paragon-software.com: fixed evcn check]

References

NVD — CVE-2026-90199 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90199
git.kernel.org/stable/c/0441e34ce0... WEB
https://git.kernel.org/stable/c/0441e34ce098c19185a7b52c5b8b89a8a5b26888
git.kernel.org/stable/c/20fd9f64c0... WEB
https://git.kernel.org/stable/c/20fd9f64c0050658f2031e6bd5d552c6f0c8f7e3
git.kernel.org/stable/c/2b9a0e57bf... WEB
https://git.kernel.org/stable/c/2b9a0e57bfd365e2096706b19ae34dce3b4a884b
git.kernel.org/stable/c/7ab69cef49... WEB
https://git.kernel.org/stable/c/7ab69cef49ebdfee288287d62641b24ab1445ecc
git.kernel.org/stable/c/ce9a619c43... WEB
https://git.kernel.org/stable/c/ce9a619c432b9a4044fee115c5483fbed946c131

Frequently Asked Questions

What is CVE-2026-90199?
CVE-2026-90199 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-90199?
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-90199?
CVE-2026-90199 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-90199?
CVE-2026-90199 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90199?
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-6r4v-32r5-fpv2",
  "modified" : "2026-09-18T18:31:27Z",
  "published" : "2026-09-17T18:31:55Z",
  "aliases" : [ "CVE-2026-90199" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: reject out-of-range evcn in mi_enum_attr()\n\nIn mi_enum_attr(), the start/end VCN validation for non-resident\nattributes is:\n\n\tif (svcn > evcn + 1) goto out;\n\nWhen evcn is U64_MAX the \"evcn + 1\" expression wraps to 0 and any svcn\npasses the check. For evcn values close to U64_MAX (but not equal to it)\nthe right-hand side is still a meaningless near-wrap upper bound, so a\nmalformed on-disk attribute with svcn == 0 and evcn near U64_MAX can pass\nmi_enum_attr() unrejected.\n\nVCN (virtual cluster number) is a cluster index, so any valid evcn is\nbounded by the volume's total cluster count, which ntfs3 holds in\nsbi->used.bitmap.nbits (set up in ntfs_init_from_boot() before any caller\nof mi_enum_attr() runs). Reject evcn values that fall outside this range.\n\nHowever, an empty non-resident attribute (no allocated clusters) is\nlegitimately encoded with svcn == 0 and evcn == -1 (U64_MAX), e.g. via\nattr->nres.evcn = cpu_to_le64((u64)vcn - 1) with vcn == 0. That sentinel\nmust keep passing, so exclude evcn == U64_MAX from the range check. The\nexisting \"svcn > evcn + 1\" test still tolerates the sentinel (\"0 > 0\" is\nfalse) and continues to require svcn == 0 for it, while the range check\nrejects every other out-of-range evcn and thereby also defuses the\n\"evcn + 1\" wraparound.\n\nsvcn does not need its own bound: once evcn < nbits, \"svcn > evcn + 1\"\nimplies svcn <= nbits.\n\n[almaz.alexandrovich@paragon-software.com: fixed evcn check]",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90199"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0441e34ce098c19185a7b52c5b8b89a8a5b26888"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/20fd9f64c0050658f2031e6bd5d552c6f0c8f7e3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2b9a0e57bfd365e2096706b19ae34dce3b4a884b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7ab69cef49ebdfee288287d62641b24ab1445ecc"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ce9a619c432b9a4044fee115c5483fbed946c131"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:14Z"
  }
}