CVE-2026-68868: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-qfr4-ppjq-9gr3
Share
CVSS 6.5
CWE-1220
Published
Advisory Summary

CVE-2026-68868 is a MODERATE (CVSS 6.5) security vulnerability vulnerability (CWE-1220: Insufficient Granularity of Access Control) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. however, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets.. Remediation is available in the latest vendor maintenance releases.

CVE-2026-68868 at a Glance

CVE Identifier CVE-2026-68868
GHSA Identifier GHSA-qfr4-ppjq-9gr3
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-1220: Insufficient Granularity of Access Control
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-68868

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-68868, 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-1220: Insufficient Granularity of Access Control, where the product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. however, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets. 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

The Google Cloud Secret Manager secrets backend in Apache Airflow's Google provider never applied the team scope when resolving Connections and Variables: the caller's `team_name` was accepted by the backend but dropped at the internal call boundary, so every lookup resolved against the team-agnostic secret name. In a deployment running multi-team mode with this backend, a task or Dag belonging to one team resolved another team's Connection or Variable, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend. Users are advised to upgrade to apache-airflow-providers-google 22.3.0 or later, which builds and applies the team-scoped secret name.

References

NVD — CVE-2026-68868 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68868
Software Source Repository REPOSITORY
https://github.com/apache/airflow/pull/70869
lists.apache.org/thread/03h5y0fmqlh0... WEB
https://lists.apache.org/thread/03h5y0fmqlh0yf055zlocxh591ozx69x
Software Security Information SECURITY
http://www.openwall.com/lists/oss-security/2026/08/12/3

Frequently Asked Questions

What is CVE-2026-68868?
CVE-2026-68868 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-1220: Insufficient Granularity of Access Control.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-68868?
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-68868?
CVE-2026-68868 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-68868?
CVE-2026-68868 is classified under CWE-1220: Insufficient Granularity of Access Control (The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets.).
How can I check Maven dependencies for CVE-2026-68868?
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-qfr4-ppjq-9gr3",
  "modified" : "2026-08-12T18:31:16Z",
  "published" : "2026-08-12T12:32:54Z",
  "aliases" : [ "CVE-2026-68868" ],
  "details" : "The Google Cloud Secret Manager secrets backend in Apache Airflow's Google provider never applied the team scope when resolving Connections and Variables: the caller's `team_name` was accepted by the backend but dropped at the internal call boundary, so every lookup resolved against the team-agnostic secret name. In a deployment running multi-team mode with this backend, a task or Dag belonging to one team resolved another team's Connection or Variable, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend. Users are advised to upgrade to apache-airflow-providers-google 22.3.0 or later, which builds and applies the team-scoped secret name.",
  "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-68868"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/apache/airflow/pull/70869"
  }, {
    "type" : "WEB",
    "url" : "https://lists.apache.org/thread/03h5y0fmqlh0yf055zlocxh591ozx69x"
  }, {
    "type" : "WEB",
    "url" : "http://www.openwall.com/lists/oss-security/2026/08/12/3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1220" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-12T11:17:10Z"
  }
}