CVE-2026-72487: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-8mf8-73cp-cjmq
CVSS 7.7
Published
Advisory Summary

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

CVE-2026-72487 at a Glance

CVE Identifier CVE-2026-72487
GHSA Identifier GHSA-8mf8-73cp-cjmq
Severity HIGH
CVSS v3.1 Base Score 7.7
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.7

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:N/S:U/C:H/I:N/A:H).

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

How to Fix CVE-2026-72487

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-72487, 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: Check ROM header and data structure addr before accessing We meet a crash when running stress-ng on x86_64 machine: BUG: unable to handle page fault for address: ffa0000007f40000 RIP: 0010:pci_get_rom_size+0x52/0x220 Call Trace: <TASK> pci_map_rom+0x80/0x130 pci_read_rom+0x4b/0xe0 kernfs_file_read_iter+0x96/0x180 vfs_read+0x1b1/0x300 Our analysis reveals that the ROM space's start address is 0xffa0000007f30000, and size is 0x10000. Because of broken ROM space, before calling readl(pds), the pds's value is 0xffa0000007f3ffff, which is already pointed to the ROM space end, invoking readl() would read 4 bytes therefore cause an out-of-bounds access and trigger a crash. Fix this by adding image header and data structure checking. We also found another crash on arm64 machine: Unable to handle kernel paging request at virtual address ffff8000dd1393ff Mem abort info: ESR = 0x0000000096000021 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x21: alignment fault The call trace is the same with x86_64, but the crash reason is that the data structure addr is not aligned with 4, and arm64 machine report "alignment fault". Fix this by adding alignment checking. [bhelgaas: shorten function names, wrap comments]

References

Frequently Asked Questions

What is CVE-2026-72487?
CVE-2026-72487 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-72487?
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-72487?
CVE-2026-72487 has a CVSS v3.1 base score of 7.7 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H.
What CWE is associated with CVE-2026-72487?
CVE-2026-72487 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-72487?
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
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8mf8-73cp-cjmq",
  "modified" : "2026-08-17T06:33:32Z",
  "published" : "2026-08-15T06:32:26Z",
  "aliases" : [ "CVE-2026-72487" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nPCI: Check ROM header and data structure addr before accessing\n\nWe meet a crash when running stress-ng on x86_64 machine:\n\n  BUG: unable to handle page fault for address: ffa0000007f40000\n  RIP: 0010:pci_get_rom_size+0x52/0x220\n  Call Trace:\n  <TASK>\n    pci_map_rom+0x80/0x130\n    pci_read_rom+0x4b/0xe0\n    kernfs_file_read_iter+0x96/0x180\n    vfs_read+0x1b1/0x300\n\nOur analysis reveals that the ROM space's start address is\n0xffa0000007f30000, and size is 0x10000. Because of broken ROM space,\nbefore calling readl(pds), the pds's value is 0xffa0000007f3ffff, which is\nalready pointed to the ROM space end, invoking readl() would read 4 bytes\ntherefore cause an out-of-bounds access and trigger a crash.  Fix this by\nadding image header and data structure checking.\n\nWe also found another crash on arm64 machine:\n\n  Unable to handle kernel paging request at virtual address ffff8000dd1393ff\n  Mem abort info:\n  ESR = 0x0000000096000021\n  EC = 0x25: DABT (current EL), IL = 32 bits\n  SET = 0, FnV = 0\n  EA = 0, S1PTW = 0\n  FSC = 0x21: alignment fault\n\nThe call trace is the same with x86_64, but the crash reason is that the\ndata structure addr is not aligned with 4, and arm64 machine report\n\"alignment fault\". Fix this by adding alignment checking.\n\n[bhelgaas: shorten function names, wrap comments]",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-72487"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1d495446ec7ace5b61da366ffb161ee8319dd9a2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4997873e3abbad47a9e1e4abd05f045f77a74f22"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/538796b807fcfb81b2ce40cc97a614fd8588feb5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/721ad5b72448b5065ed309017ab563205f162404"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/724042f8f98d2594b9d164549fd4292c6bd58120"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cd5b242d5848369b9e957340a7e30adee7b6763d"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-15T06:22:22Z"
  }
}