CVE-2026-31773: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-vm8r-x97v-544j
Share
CVSS 8.8
CWE-287
Published
Advisory Summary

CVE-2026-31773 is a HIGH (CVSS 8.8) security vulnerability vulnerability (CWE-287: Improper Authentication) affecting Software libraries in the Maven ecosystem. The weakness occurs when when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-31773 at a Glance

CVE Identifier CVE-2026-31773
GHSA Identifier GHSA-vm8r-x97v-544j
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-287: Improper Authentication
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.8

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:H/I:H/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 High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-31773

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-31773, 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 CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. 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: Bluetooth: SMP: derive legacy responder STK authentication from MITM state The legacy responder path in smp_random() currently labels the stored STK as authenticated whenever pending_sec_level is BT_SECURITY_HIGH. That reflects what the local service requested, not what the pairing flow actually achieved. For Just Works/Confirm legacy pairing, SMP_FLAG_MITM_AUTH stays clear and the resulting STK should remain unauthenticated even if the local side requested HIGH security. Use the established MITM state when storing the responder STK so the key metadata matches the pairing result. This also keeps the legacy path aligned with the Secure Connections code, which already treats JUST_WORKS/JUST_CFM as unauthenticated.

References

NVD — CVE-2026-31773 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-31773
git.kernel.org/stable/c/061ee71ac6... WEB
https://git.kernel.org/stable/c/061ee71ac6b03c9f8432fe49538c3682bfcf4cf3
git.kernel.org/stable/c/0afc846bd8... WEB
https://git.kernel.org/stable/c/0afc846bd80073ffcd2b8040f2b2fafaea3d9f72
git.kernel.org/stable/c/20756fec2f... WEB
https://git.kernel.org/stable/c/20756fec2f0108cb88e815941f1ffff88dc286fe
git.kernel.org/stable/c/667f44f139... WEB
https://git.kernel.org/stable/c/667f44f1392df6482483756458c48670e579e9ff
git.kernel.org/stable/c/929db734d1... WEB
https://git.kernel.org/stable/c/929db734d12db41ca5f95424db4612397f1bd4a7
git.kernel.org/stable/c/9a38659a3d... WEB
https://git.kernel.org/stable/c/9a38659a3d06080715691bd3139f9c4b61f688e3
git.kernel.org/stable/c/9a6d0db176... WEB
https://git.kernel.org/stable/c/9a6d0db176f082685e0b6149700c0baf3ce2aa8b
git.kernel.org/stable/c/b1c6a8e554... WEB
https://git.kernel.org/stable/c/b1c6a8e554a39b222c0879a288ea98e338fc4d77

Frequently Asked Questions

What is CVE-2026-31773?
CVE-2026-31773 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-287: Improper Authentication.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-31773?
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-31773?
CVE-2026-31773 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-31773?
CVE-2026-31773 is classified under CWE-287: Improper Authentication (When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.).
How can I check Maven dependencies for CVE-2026-31773?
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-vm8r-x97v-544j",
  "modified" : "2026-05-03T09:33:10Z",
  "published" : "2026-05-01T15:30:35Z",
  "aliases" : [ "CVE-2026-31773" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: SMP: derive legacy responder STK authentication from MITM state\n\nThe legacy responder path in smp_random() currently labels the stored\nSTK as authenticated whenever pending_sec_level is BT_SECURITY_HIGH.\nThat reflects what the local service requested, not what the pairing\nflow actually achieved.\n\nFor Just Works/Confirm legacy pairing, SMP_FLAG_MITM_AUTH stays clear\nand the resulting STK should remain unauthenticated even if the local\nside requested HIGH security. Use the established MITM state when\nstoring the responder STK so the key metadata matches the pairing result.\n\nThis also keeps the legacy path aligned with the Secure Connections code,\nwhich already treats JUST_WORKS/JUST_CFM as unauthenticated.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:A/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-31773"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/061ee71ac6b03c9f8432fe49538c3682bfcf4cf3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0afc846bd80073ffcd2b8040f2b2fafaea3d9f72"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/20756fec2f0108cb88e815941f1ffff88dc286fe"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/667f44f1392df6482483756458c48670e579e9ff"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/929db734d12db41ca5f95424db4612397f1bd4a7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9a38659a3d06080715691bd3139f9c4b61f688e3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9a6d0db176f082685e0b6149700c0baf3ce2aa8b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b1c6a8e554a39b222c0879a288ea98e338fc4d77"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-287" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-05-01T15:16:40Z"
  }
}