CVE-2026-93203: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-jrfx-xv62-wfwq
Share
CVSS 7.1
Published
Advisory Summary

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

CVE-2026-93203 at a Glance

CVE Identifier CVE-2026-93203
GHSA Identifier GHSA-jrfx-xv62-wfwq
Severity HIGH
CVSS v3.1 Base Score 7.1
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.1

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

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

How to Fix CVE-2026-93203

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-93203, 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: batman-adv: bla: avoid CRC corruption due to parallel claim add batadv_bla_add_claim() is used to add claims and modify the backbone of claims for CLAIM frames from remote backbones and local packets. When it handles a claim, it needs to either * add the new claim's CRC to the backbone CRC * remove the already existing claim's CRC from the old backbone and add it to the new backbone But when the "new" claim code was running in parallel to the "change backbone" code, it can happen that the CRC was invalid because the backbone_gw of the claim was changed twice in the "new" claim code path: * CPU0 creates the claim for gateway A and publishes it in the claim hash. The crc16 of the address has not yet been added to A's crc at this point. * CPU1 processes a claim frame of gateway B for the same client, finds the just published claim, and performs the ownership change: it switches the pointer to B, removes the crc16 from A's crc - which never contained it - and adds it to B's crc. * CPU0 continues behind the creation branch, unconditionally switches the pointer back to A without compensating B's crc (its remove_crc is false for the creation path), and finally adds the crc16 to A's crc The CRC is then wrong for both: * claim belongs to A: but CRC is not part of backbone A's CRC * claim doesn't belong to B: CRC is still part of backbone B's CRC This wrong CRC is never recomputated from the stored claims. For local backbone claims, this can also not recovered using syncs. To avoid this, split the functionality in clear separate parts: * new claim which always adds claim CRC to the backbone CRC (but never changes the already set backbone_gw of the claim back) * update of existing claim which automatically changes the backbone_gw entry and only updates both backbone CRCs when there was an actual change

References

NVD — CVE-2026-93203 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93203
git.kernel.org/stable/c/08645ab957... WEB
https://git.kernel.org/stable/c/08645ab95768b88e2ff85a89211994651710465b
git.kernel.org/stable/c/1d390db003... WEB
https://git.kernel.org/stable/c/1d390db003cbb52cdd86837608bff3794501a5ea
git.kernel.org/stable/c/3d4a9ae2c6... WEB
https://git.kernel.org/stable/c/3d4a9ae2c69c0fe4c3c69587288241243bb7a39b
git.kernel.org/stable/c/8bcfa58c42... WEB
https://git.kernel.org/stable/c/8bcfa58c4277bff1882a23547c37ab08aa1de12f
git.kernel.org/stable/c/a3e07db74f... WEB
https://git.kernel.org/stable/c/a3e07db74f22a85aeeb51c600da5c98b9cbca11f
git.kernel.org/stable/c/ad982d925f... WEB
https://git.kernel.org/stable/c/ad982d925f00d860d2467811256ffadcccd9e4a7
git.kernel.org/stable/c/d5b0e7574d... WEB
https://git.kernel.org/stable/c/d5b0e7574da5a485f4dbec32a15911900a4487c2
git.kernel.org/stable/c/e54602d9e3... WEB
https://git.kernel.org/stable/c/e54602d9e38db8573f2097d60c7ea8be0a5af1fa

Frequently Asked Questions

What is CVE-2026-93203?
CVE-2026-93203 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-93203?
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-93203?
CVE-2026-93203 has a CVSS v3.1 base score of 7.1 (HIGH) with vector string CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H.
What CWE is associated with CVE-2026-93203?
CVE-2026-93203 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93203?
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-jrfx-xv62-wfwq",
  "modified" : "2026-09-18T18:31:35Z",
  "published" : "2026-09-17T18:32:14Z",
  "aliases" : [ "CVE-2026-93203" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbatman-adv: bla: avoid CRC corruption due to parallel claim add\n\nbatadv_bla_add_claim() is used to add claims and modify the backbone of\nclaims for CLAIM frames from remote backbones and local packets. When it\nhandles a claim, it needs to either\n\n* add the new claim's CRC to the backbone CRC\n* remove the already existing claim's CRC from the old backbone and add it\n  to the new backbone\n\nBut when the \"new\" claim code was running in parallel to the \"change\nbackbone\" code, it can happen that the CRC was invalid because the\nbackbone_gw of the claim was changed twice in the \"new\" claim code path:\n\n* CPU0 creates the claim for gateway A and publishes it in the claim\n  hash. The crc16 of the address has not yet been added to A's crc at\n  this point.\n\n* CPU1 processes a claim frame of gateway B for the same client, finds\n  the just published claim, and performs the ownership change: it\n  switches the pointer to B, removes the crc16 from A's crc - which\n  never contained it - and adds it to B's crc.\n\n* CPU0 continues behind the creation branch, unconditionally switches\n  the pointer back to A without compensating B's crc (its remove_crc\n  is false for the creation path), and finally adds the crc16 to A's\n  crc\n\nThe CRC is then wrong for both:\n\n* claim belongs to A: but CRC is not part of backbone A's CRC\n* claim doesn't belong to B: CRC is still part of backbone B's CRC\n\nThis wrong CRC is never recomputated from the stored claims. For local\nbackbone claims, this can also not recovered using syncs.\n\nTo avoid this, split the functionality in clear separate parts:\n\n* new claim which always adds claim CRC to the backbone CRC (but never\n  changes the already set backbone_gw of the claim back)\n\n* update of existing claim which automatically changes the backbone_gw\n  entry and only updates both backbone CRCs when there was an actual change",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93203"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/08645ab95768b88e2ff85a89211994651710465b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1d390db003cbb52cdd86837608bff3794501a5ea"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/3d4a9ae2c69c0fe4c3c69587288241243bb7a39b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8bcfa58c4277bff1882a23547c37ab08aa1de12f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a3e07db74f22a85aeeb51c600da5c98b9cbca11f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ad982d925f00d860d2467811256ffadcccd9e4a7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d5b0e7574da5a485f4dbec32a15911900a4487c2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e54602d9e38db8573f2097d60c7ea8be0a5af1fa"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:18:16Z"
  }
}