CVE-2026-93206: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-fjc2-7frc-hj2c
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-93206
GHSA Identifier GHSA-fjc2-7frc-hj2c
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-93206

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-93206, 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: PCI/proc: Use file_ns_capable() when checking config space read access proc_bus_pci_read() decides how much of the config space is readable based on capable(CAP_SYS_ADMIN), which checks the credentials of the task calling read(), not the credentials of the process that opened the file. The sysfs equivalent, pci_read_config(), has checked the credentials of the opening process since commit de139a339395 ("pci: check caps from sysfs file open to read device dependent config space"), so a privileged process can open the config space file and pass the file descriptor to an unprivileged process (for example, a process running a KVM guest with an assigned device), which can then read the entire config space. The check was subsequently routed through the LSM framework in commit 47970b1b2aa6 ("pci: use security_capable() when checking capablities during config space read") and converted to the dedicated helper in commit ab0fa82b2df9 ("pci-sysfs: use proper file capability helper function"). Thus, the two interfaces check the same capability against different credentials. Checking the credentials of the task calling read() makes the outcome depend on who reads rather than who opened, so the restriction is bypassed whenever a more privileged process reads through the descriptor. Checking the credentials recorded in file->f_cred settles the decision at open() time and ties it to the file, where it cannot change with the caller. Use file_ns_capable() to check CAP_SYS_ADMIN against the credentials in effect when the file was opened, bringing the procfs interface in line with the sysfs behaviour. As a result, a file descriptor opened by a privileged process and passed to an unprivileged one now allows the entire config space to be read through procfs, matching sysfs.

References

NVD — CVE-2026-93206 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93206
git.kernel.org/stable/c/53407535d4... WEB
https://git.kernel.org/stable/c/53407535d49ec034e476121020b5c878f0d92e18
git.kernel.org/stable/c/5c7ab4ca66... WEB
https://git.kernel.org/stable/c/5c7ab4ca66f0880cffc3735555ea719dd5253726
git.kernel.org/stable/c/6351e94076... WEB
https://git.kernel.org/stable/c/6351e94076329dab517ea94c115e15c4d8459381
git.kernel.org/stable/c/77272b7fd0... WEB
https://git.kernel.org/stable/c/77272b7fd0e472086fd626a1fcd11da625822cc2
git.kernel.org/stable/c/8a3a54aa3e... WEB
https://git.kernel.org/stable/c/8a3a54aa3e65ed76f8560a387243a7738ae0cb1c
git.kernel.org/stable/c/c2d4174f49... WEB
https://git.kernel.org/stable/c/c2d4174f492458ecdcdef309243624999612d526
git.kernel.org/stable/c/e7730acd6a... WEB
https://git.kernel.org/stable/c/e7730acd6a01c5931a3afb83639810ff2fb9cc92
git.kernel.org/stable/c/f82f53e75e... WEB
https://git.kernel.org/stable/c/f82f53e75eff382fc8f56b73279b54f7cf5a5c65

Frequently Asked Questions

What is CVE-2026-93206?
CVE-2026-93206 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-93206?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-93206?
CVE-2026-93206 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93206?
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-fjc2-7frc-hj2c",
  "modified" : "2026-09-24T18:31:21Z",
  "published" : "2026-09-24T18:31:21Z",
  "aliases" : [ "CVE-2026-93206" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nPCI/proc: Use file_ns_capable() when checking config space read access\n\nproc_bus_pci_read() decides how much of the config space is readable based\non capable(CAP_SYS_ADMIN), which checks the credentials of the task calling\nread(), not the credentials of the process that opened the file.\n\nThe sysfs equivalent, pci_read_config(), has checked the credentials of the\nopening process since commit de139a339395 (\"pci: check caps from sysfs file\nopen to read device dependent config space\"), so a privileged process can\nopen the config space file and pass the file descriptor to an unprivileged\nprocess (for example, a process running a KVM guest with an assigned\ndevice), which can then read the entire config space.  The check was\nsubsequently routed through the LSM framework in commit 47970b1b2aa6 (\"pci:\nuse security_capable() when checking capablities during config space read\")\nand converted to the dedicated helper in commit ab0fa82b2df9 (\"pci-sysfs:\nuse proper file capability helper function\").\n\nThus, the two interfaces check the same capability against different\ncredentials.  Checking the credentials of the task calling read() makes the\noutcome depend on who reads rather than who opened, so the restriction is\nbypassed whenever a more privileged process reads through the descriptor.\nChecking the credentials recorded in file->f_cred settles the decision at\nopen() time and ties it to the file, where it cannot change with the\ncaller.\n\nUse file_ns_capable() to check CAP_SYS_ADMIN against the credentials in\neffect when the file was opened, bringing the procfs interface in line with\nthe sysfs behaviour.\n\nAs a result, a file descriptor opened by a privileged process and passed to\nan unprivileged one now allows the entire config space to be read through\nprocfs, matching sysfs.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93206"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/53407535d49ec034e476121020b5c878f0d92e18"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5c7ab4ca66f0880cffc3735555ea719dd5253726"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6351e94076329dab517ea94c115e15c4d8459381"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/77272b7fd0e472086fd626a1fcd11da625822cc2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/8a3a54aa3e65ed76f8560a387243a7738ae0cb1c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c2d4174f492458ecdcdef309243624999612d526"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e7730acd6a01c5931a3afb83639810ff2fb9cc92"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f82f53e75eff382fc8f56b73279b54f7cf5a5c65"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-24T16:17:14Z"
  }
}