CVE-2026-43266: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-r9ph-9m45-xj6w
CVSS 5.5
Published
Advisory Summary

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

CVE-2026-43266 at a Glance

CVE Identifier CVE-2026-43266
GHSA Identifier GHSA-r9ph-9m45-xj6w
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

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

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

How to Fix CVE-2026-43266

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-43266, 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: EFI/CPER: don't go past the ARM processor CPER record buffer There's a logic inside GHES/CPER to detect if the section_length is too small, but it doesn't detect if it is too big. Currently, if the firmware receives an ARM processor CPER record stating that a section length is big, kernel will blindly trust section_length, producing a very long dump. For instance, a 67 bytes record with ERR_INFO_NUM set 46198 and section length set to 854918320 would dump a lot of data going a way past the firmware memory-mapped area. Fix it by adding a logic to prevent it to go past the buffer if ERR_INFO_NUM is too big, making it report instead: [Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1 [Hardware Error]: event severity: recoverable [Hardware Error]: Error 0, type: recoverable [Hardware Error]: section_type: ARM processor error [Hardware Error]: MIDR: 0xff304b2f8476870a [Hardware Error]: section length: 854918320, CPER size: 67 [Hardware Error]: section length is too big [Hardware Error]: firmware-generated error record is incorrect [Hardware Error]: ERR_INFO_NUM is 46198 [ rjw: Subject and changelog tweaks ]

References

Frequently Asked Questions

What is CVE-2026-43266?
CVE-2026-43266 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-43266?
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-43266?
CVE-2026-43266 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-43266?
CVE-2026-43266 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-43266?
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-r9ph-9m45-xj6w",
  "modified" : "2026-05-08T21:31:21Z",
  "published" : "2026-05-06T12:30:35Z",
  "aliases" : [ "CVE-2026-43266" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nEFI/CPER: don't go past the ARM processor CPER record buffer\n\nThere's a logic inside GHES/CPER to detect if the section_length\nis too small, but it doesn't detect if it is too big.\n\nCurrently, if the firmware receives an ARM processor CPER record\nstating that a section length is big, kernel will blindly trust\nsection_length, producing a very long dump. For instance, a 67\nbytes record with ERR_INFO_NUM set 46198 and section length\nset to 854918320 would dump a lot of data going a way past the\nfirmware memory-mapped area.\n\nFix it by adding a logic to prevent it to go past the buffer\nif ERR_INFO_NUM is too big, making it report instead:\n\n\t[Hardware Error]: Hardware error from APEI Generic Hardware Error Source: 1\n\t[Hardware Error]: event severity: recoverable\n\t[Hardware Error]:  Error 0, type: recoverable\n\t[Hardware Error]:   section_type: ARM processor error\n\t[Hardware Error]:   MIDR: 0xff304b2f8476870a\n\t[Hardware Error]:   section length: 854918320, CPER size: 67\n\t[Hardware Error]:   section length is too big\n\t[Hardware Error]:   firmware-generated error record is incorrect\n\t[Hardware Error]:   ERR_INFO_NUM is 46198\n\n[ rjw: Subject and changelog tweaks ]",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-43266"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/25b290624b0e3d2f0f90238709ee0b6009b9fde8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/45766863baf899059e75595dd3cb1116467f2095"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/64eb63f573f497553e1a0c388bbcdd639e0f0704"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a68d22902a6916e10ee235fee609239004e129d0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/be10c1bdf64a39832998f54900aa309b3917abcf"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c80113dcfc807308f5ab33847fae77e07531aeb8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ca2aad8771aa9091bc9e42e7d546bd40b72ddcd4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/eae21beecb95a3b69ee5c38a659f774e171d730e"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-05-06T12:16:47Z"
  }
}