FKIE_CVE-2026-53561

Vulnerability from fkie_nvd - Published: 2026-08-25 11:16 - Updated: 2026-09-28 23:10
Severity
7.4 (High) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Summary
An improper authentication vulnerability in HiveServer2 SAML bearer-token validation in Apache Hive 4.0.0 through 4.2.0 (and later unreleased branches) on deployments using HTTP transport with hive.server2.authentication=SAML allows an unauthenticated network attacker to authenticate as an arbitrary Hive user and obtain an authenticated HiveServer2 session via a forged Authorization: Bearer token sent to the /cliservice HTTP endpoint. Users are recommended to upgrade to 4.2.1 version that includes the fix for this issue. Access / authorization required: No Hive credentials, SAML IdP login, or knowledge of the server signing secret is required. The attacker only needs network reachability to the HiveServer2 HTTP port (typically /cliservice), directly or through a reverse proxy such as Apache Knox that forwards unauthenticated requests to HS2. The instance must have SAML authentication enabled in HTTP mode. Deployments where Knox handles SSO and HiveServer2 uses LDAP/Kerberos (not native SAML mode) are not affected by this specific issue.
References
security@apache.orghttps://github.com/apache/hiveProduct
security@apache.orghttps://github.com/apache/hive/commit/6ca06ca1104ff7462363087a867d70d546134774Patch
security@apache.orghttps://issues.apache.org/jira/browse/HIVE-29653Vendor Advisory
security@apache.orghttps://lists.apache.org/thread/6d56mk501fp4f8cb5wvrpj2jwd9knt05Mailing List, Vendor Advisory
Impacted products
Vendor Product Version
apache hive *
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "collectionURL": "https://repo.maven.apache.org/maven2",
          "defaultStatus": "unaffected",
          "packageName": "org.apache.hive:hive-service",
          "product": "Apache Hive",
          "vendor": "Apache Software Foundation",
          "versions": [
            {
              "lessThanOrEqual": "4.2.0",
              "status": "affected",
              "version": "4.0.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "source": "security@apache.org"
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:apache:hive:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "294FE7F2-2372-4E50-9CB5-6F9EEFB5D57E",
              "versionEndExcluding": "4.2.1",
              "versionStartIncluding": "4.0.0",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "An improper authentication vulnerability in HiveServer2 SAML bearer-token validation in Apache Hive 4.0.0 through 4.2.0 (and later unreleased branches) on deployments using HTTP transport with hive.server2.authentication=SAML allows an unauthenticated network attacker to authenticate as an arbitrary Hive user and obtain an authenticated HiveServer2 session via a forged Authorization: Bearer token sent to the /cliservice HTTP endpoint. Users are recommended to upgrade to 4.2.1 version that includes the fix for this issue.\n\nAccess / authorization required: No Hive credentials, SAML IdP login, or knowledge of the server signing secret is required. The attacker only needs network reachability to the HiveServer2 HTTP port (typically /cliservice), directly or through a reverse proxy such as Apache Knox that forwards unauthenticated requests to HS2. The instance must have SAML authentication enabled in HTTP mode. Deployments where Knox handles SSO and HiveServer2 uses LDAP/Kerberos (not native SAML mode) are not affected by this specific issue."
    },
    {
      "lang": "es",
      "value": "Una vulnerabilidad de autenticaci\u00f3n impropia en la validaci\u00f3n de tokens portadores SAML de HiveServer2 en Apache Hive 4.0.0 hasta 4.2.0 (y ramas posteriores no publicadas) en despliegues que usan transporte HTTP con hive.server2.authentication=SAML permite a un atacante de red no autenticado autenticarse como un usuario Hive arbitrario y obtener una sesi\u00f3n de HiveServer2 autenticada a trav\u00e9s de un token \u0027Authorization: Bearer\u0027 falsificado enviado al endpoint HTTP /cliservice. Se recomienda a los usuarios actualizar a la versi\u00f3n 4.2.1 que incluye la correcci\u00f3n para este problema.\n\nAcceso / autorizaci\u00f3n requerida: No se requieren credenciales de Hive, inicio de sesi\u00f3n de SAML IdP, ni conocimiento del secreto de firma del servidor. El atacante solo necesita accesibilidad de red al puerto HTTP de HiveServer2 (t\u00edpicamente /cliservice), directamente o a trav\u00e9s de un proxy inverso como Apache Knox que reenv\u00eda solicitudes no autenticadas a HS2. La instancia debe tener la autenticaci\u00f3n SAML habilitada en modo HTTP. Los despliegues donde Knox maneja el SSO y HiveServer2 usa LDAP/Kerberos (no en modo SAML nativo) no se ven afectados por este problema espec\u00edfico."
    }
  ],
  "id": "CVE-2026-53561",
  "lastModified": "2026-09-28T23:10:00.143",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 7.4,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.2,
        "impactScore": 5.2,
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-53561",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-08-26T18:48:48.929691Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2026-08-25T11:16:53.543",
  "references": [
    {
      "source": "security@apache.org",
      "tags": [
        "Product"
      ],
      "url": "https://github.com/apache/hive"
    },
    {
      "source": "security@apache.org",
      "tags": [
        "Patch"
      ],
      "url": "https://github.com/apache/hive/commit/6ca06ca1104ff7462363087a867d70d546134774"
    },
    {
      "source": "security@apache.org",
      "tags": [
        "Vendor Advisory"
      ],
      "url": "https://issues.apache.org/jira/browse/HIVE-29653"
    },
    {
      "source": "security@apache.org",
      "tags": [
        "Mailing List",
        "Vendor Advisory"
      ],
      "url": "https://lists.apache.org/thread/6d56mk501fp4f8cb5wvrpj2jwd9knt05"
    }
  ],
  "sourceIdentifier": "security@apache.org",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-287"
        },
        {
          "lang": "en",
          "value": "CWE-305"
        },
        {
          "lang": "en",
          "value": "CWE-345"
        }
      ],
      "source": "security@apache.org",
      "type": "Secondary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.