CVE-2026-53081: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-phj2-v9xx-8m7r
CVSS 7.8
CWE-386
Published
Advisory Summary

CVE-2026-53081 is a HIGH (CVSS 7.8) security vulnerability vulnerability (CWE-386: Symbolic Name not Mapping to Correct Object) affecting Software libraries in the Maven ecosystem. The weakness occurs when a constant symbolic reference to an object is used, even though the reference can resolve to a different object over time.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-53081 at a Glance

CVE Identifier CVE-2026-53081
GHSA Identifier GHSA-phj2-v9xx-8m7r
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification CWE-386: Symbolic Name not Mapping to Correct Object
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

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

How to Fix CVE-2026-53081

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-53081, 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-386: Symbolic Name not Mapping to Correct Object, where a constant symbolic reference to an object is used, even though the reference can resolve to a different object over time. 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: bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars When regsafe() compares two scalar registers that both carry BPF_ADD_CONST, check_scalar_ids() maps their full compound id (aka base | BPF_ADD_CONST flag) as one idmap entry. However, it never verifies that the underlying base ids, that is, with the flag stripped are consistent with existing idmap mappings. This allows construction of two verifier states where the old state has R3 = R2 + 10 (both sharing base id A) while the current state has R3 = R4 + 10 (base id C, unrelated to R2). The idmap creates two independent entries: A->B (for R2) and A|flag->C|flag (for R3), without catching that A->C conflicts with A->B. State pruning then incorrectly succeeds. Fix this by additionally verifying base ID mapping consistency whenever BPF_ADD_CONST is set: after mapping the compound ids, also invoke check_ids() on the base IDs (flag bits stripped). This ensures that if A was already mapped to B from comparing the source register, any ADD_CONST derivative must also derive from B, not an unrelated C.

References

Frequently Asked Questions

What is CVE-2026-53081?
CVE-2026-53081 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-386: Symbolic Name not Mapping to Correct Object.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-53081?
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-53081?
CVE-2026-53081 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-53081?
CVE-2026-53081 is classified under CWE-386: Symbolic Name not Mapping to Correct Object (A constant symbolic reference to an object is used, even though the reference can resolve to a different object over time.).
How can I check Maven dependencies for CVE-2026-53081?
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-phj2-v9xx-8m7r",
  "modified" : "2026-06-30T03:37:13Z",
  "published" : "2026-06-24T18:32:46Z",
  "aliases" : [ "CVE-2026-53081" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars\n\nWhen regsafe() compares two scalar registers that both carry\nBPF_ADD_CONST, check_scalar_ids() maps their full compound id\n(aka base | BPF_ADD_CONST flag) as one idmap entry. However,\nit never verifies that the underlying base ids, that is, with\nthe flag stripped are consistent with existing idmap mappings.\n\nThis allows construction of two verifier states where the old\nstate has R3 = R2 + 10 (both sharing base id A) while the current\nstate has R3 = R4 + 10 (base id C, unrelated to R2). The idmap\ncreates two independent entries: A->B (for R2) and A|flag->C|flag\n(for R3), without catching that A->C conflicts with A->B. State\npruning then incorrectly succeeds.\n\nFix this by additionally verifying base ID mapping consistency\nwhenever BPF_ADD_CONST is set: after mapping the compound ids,\nalso invoke check_ids() on the base IDs (flag bits stripped).\nThis ensures that if A was already mapped to B from comparing\nthe source register, any ADD_CONST derivative must also derive\nfrom B, not an unrelated C.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-53081"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/security/cve/CVE-2026-53081"
  }, {
    "type" : "WEB",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2492322"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/13c02881e49aac4c82b261faa26db9edf2567231"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2f2ec8e7730e21fc9bd49e0de9cdd58213ea24d0"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/691adf738817275368ed56311b7d798d617823a3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7d73c72cccac651acc891377a5e623e4021c6380"
  }, {
    "type" : "WEB",
    "url" : "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53081.json"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-386" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-06-24T17:17:22Z"
  }
}