CVE-2026-86465: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-rmjj-53pr-xrwc
Share
CVSS 6.5
CWE-639
Published
Advisory Summary

CVE-2026-86465 is a MODERATE (CVSS 6.5) security vulnerability vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) affecting Software libraries in the Maven ecosystem. The weakness occurs when the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-86465 at a Glance

CVE Identifier CVE-2026-86465
GHSA Identifier GHSA-rmjj-53pr-xrwc
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-639: Authorization Bypass Through User-Controlled Key
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 6.5

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

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

How to Fix CVE-2026-86465

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-86465, 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-639: Authorization Bypass Through User-Controlled Key, where the system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. 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

Apache Airflow Akeyless provider: the Akeyless secrets backend's team-scope guard can be bypassed with a user-controlled key. In a multi-team deployment, a Dag author scoped to one team can supply a Variable key containing a path separator that causes the backend to resolve a secret belonging to a different team, because the lookup path is concatenated from an unvalidated key after the team-scoped lookup misses. The Execution API Variables route accepts a path-shaped key, so this is reachable from ordinary Dag code. Affects multi-team deployments using the Akeyless secrets backend. Single-team deployments are not affected, as there is no cross-team boundary to cross. This is the same class as CVE-2026-68870, CVE-2026-68871 and CVE-2026-68872 in the Azure Key Vault, Yandex Lockbox and Amazon secrets backends. Users of apache-airflow-providers-akeyless are recommended to upgrade to version 0.3.1 or later, which fixes the issue.

References

NVD — CVE-2026-86465 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-86465
Software Source Repository REPOSITORY
https://github.com/apache/airflow/pull/72646
lists.apache.org/thread/vczt5xgqjv8o... WEB
https://lists.apache.org/thread/vczt5xgqjv8ot8fpp1vdq3rmnfm50w0g
lists.apache.org/thread/vczt5xgqjv8o... WEB
https://lists.apache.org/thread/vczt5xgqjv8ot8fpp1vdq3rmnfm50w0g?users@airflow.apache.org
CVE Official Record — CVE-2026-86465 CVE
https://www.cve.org/CVERecord?id=CVE-2026-68870
CVE Official Record — CVE-2026-86465 CVE
https://www.cve.org/CVERecord?id=CVE-2026-68871
CVE Official Record — CVE-2026-86465 CVE
https://www.cve.org/CVERecord?id=CVE-2026-68872

Frequently Asked Questions

What is CVE-2026-86465?
CVE-2026-86465 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-639: Authorization Bypass Through User-Controlled Key.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-86465?
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-86465?
CVE-2026-86465 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-86465?
CVE-2026-86465 is classified under CWE-639: Authorization Bypass Through User-Controlled Key (The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.).
How can I check Maven dependencies for CVE-2026-86465?
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-rmjj-53pr-xrwc",
  "modified" : "2026-09-17T18:31:46Z",
  "published" : "2026-09-16T09:30:29Z",
  "aliases" : [ "CVE-2026-86465" ],
  "details" : "Apache Airflow Akeyless provider: the Akeyless secrets backend's team-scope guard can be bypassed with a user-controlled key. In a multi-team deployment, a Dag author scoped to one team can supply a Variable key containing a path separator that causes the backend to resolve a secret belonging to a different team, because the lookup path is concatenated from an unvalidated key after the team-scoped lookup misses. The Execution API Variables route accepts a path-shaped key, so this is reachable from ordinary Dag code.\n\nAffects multi-team deployments using the Akeyless secrets backend. Single-team deployments are not affected, as there is no cross-team boundary to cross. This is the same class as CVE-2026-68870, CVE-2026-68871 and CVE-2026-68872 in the Azure Key Vault, Yandex Lockbox and Amazon secrets backends.\n\nUsers of apache-airflow-providers-akeyless are recommended to upgrade to version 0.3.1 or later, which fixes the issue.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-86465"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/airflow/pull/72646"
  }, {
    "type" : "WEB",
    "url" : "https://lists.apache.org/thread/vczt5xgqjv8ot8fpp1vdq3rmnfm50w0g"
  }, {
    "type" : "WEB",
    "url" : "https://lists.apache.org/thread/vczt5xgqjv8ot8fpp1vdq3rmnfm50w0g?users@airflow.apache.org"
  }, {
    "type" : "WEB",
    "url" : "https://www.cve.org/CVERecord?id=CVE-2026-68870"
  }, {
    "type" : "WEB",
    "url" : "https://www.cve.org/CVERecord?id=CVE-2026-68871"
  }, {
    "type" : "WEB",
    "url" : "https://www.cve.org/CVERecord?id=CVE-2026-68872"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-639" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T09:17:07Z"
  }
}