CVE-2026-55976

{"id": "CVE-2026-55976", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-55976", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-08-26T18:50:37.199246Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.1, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.2, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security@apache.org", "affectedData": [{"vendor": "Apache Software Foundation", "product": "Apache Hive", "versions": [{"status": "affected", "version": "2.1.0", "versionType": "semver", "lessThanOrEqual": "4.2.0"}], "packageName": "org.apache.hive:hive-serde", "collectionURL": "https://repo.maven.apache.org/maven2", "defaultStatus": "unaffected"}]}], "published": "2026-08-25T11:16:53.673", "references": [{"url": "https://github.com/apache/hive", "tags": ["Product"], "source": "security@apache.org"}, {"url": "https://github.com/apache/hive/commit/45049202df35cea382616624de3fe8d252aa2d00", "tags": ["Patch"], "source": "security@apache.org"}, {"url": "https://issues.apache.org/jira/browse/HIVE-29671", "tags": ["Vendor Advisory"], "source": "security@apache.org"}, {"url": "https://lists.apache.org/thread/6d56mk501fp4f8cb5wvrpj2jwd9knt05", "tags": ["Mailing List", "Vendor Advisory"], "source": "security@apache.org"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security@apache.org", "description": [{"lang": "en", "value": "CWE-918"}]}], "descriptions": [{"lang": "en", "value": "Server-Side Request Forgery (SSRF) in Avro SerDe schema resolution in Apache Hive before 4.2.1 allows an authenticated remote attacker with CREATE TABLE privilege to cause the Hive server to fetch an attacker-controlled URL when resolving the avro.schema.url\u00a0table property on an Avro table that is subsequently queried. This can expose cloud instance metadata, internal network services, or local server files to the Hive process identity. Users are recommended to upgrade to version 4.2.1, which fixes this issue.\n\n\n\nAttacker access requirements:\n\n * Network access to HiveServer2 / Metastore: required (remote attacker model).\n * Valid Hive authentication: required.\n * CREATE TABLE (or equivalent) privilege: required, so the attacker can set avro.schema.url\u00a0in table properties.\n * SELECT privilege on the malicious table: not required for the creator, who can typically query their own table; any other user granted SELECT can also trigger the fetch.\n * Write access to the table LOCATION: not required; the attack uses the schema URL, not the data path.\n * Admin / superuser privileges: not required; an ordinary authenticated user with DDL rights is sufficient.\n * External tables enabled: typically required in practice, and enabled by default in most deployments.\n\n\n\n\nDetection guidance:\n\n * Inspect metastore / Hive table metadata for Avro tables whose avro.schema.url\u00a0uses unexpected schemes such as http, https, file, or ftp, or points at link-local / cloud metadata addresses (for example 169.254.169.254) or other internal hosts.\n * Review HiveServer2 and Metastore logs around CREATE/ALTER TABLE and queries against Avro tables for schema-resolution failures or outbound fetches of avro.schema.url.\n * Correlate CREATE TABLE / ALTER TABLE activity that sets avro.schema.url\u00a0with subsequent SELECT activity on the same table, especially when the URL target is unusual for schema distribution.\n * On cloud deployments, check instance / VPC flow logs and metadata service access logs for unexpected requests from Hive host identities shortly after Avro DDL or query activity."}, {"lang": "es", "value": "Falsificaci\u00f3n de petici\u00f3n del lado del servidor (SSRF) en la resoluci\u00f3n de esquemas Avro SerDe en Apache Hive anterior a la versi\u00f3n 4.2.1 permite a un atacante remoto autenticado con privilegio CREATE TABLE hacer que el servidor Hive obtenga una URL controlada por el atacante al resolver la propiedad de tabla avro.schema.url en una tabla Avro que es consultada posteriormente. Esto puede exponer metadatos de instancias en la nube, servicios de red internos o archivos de servidor locales a la identidad del proceso de Hive. Se recomienda a los usuarios actualizar a la versi\u00f3n 4.2.1, que corrige este problema.\n\nRequisitos de acceso del atacante:\n\n* Acceso a la red a HiveServer2 / Metastore: requerido (modelo de atacante remoto).\n* Autenticaci\u00f3n v\u00e1lida de Hive: requerida.\n* Privilegio CREATE TABLE (o equivalente): requerido, para que el atacante pueda establecer avro.schema.url en las propiedades de la tabla.\n* Privilegio SELECT en la tabla maliciosa: no requerido para el creador, quien normalmente puede consultar su propia tabla; cualquier otro usuario con privilegio SELECT tambi\u00e9n puede activar la obtenci\u00f3n.\n* Acceso de escritura a la LOCATION de la tabla: no requerido; el ataque utiliza la URL del esquema, no la ruta de los datos.\n* Privilegios de administrador / superusuario: no requeridos; un usuario autenticado ordinario con derechos DDL es suficiente.\n* Tablas externas habilitadas: t\u00edpicamente requeridas en la pr\u00e1ctica, y habilitadas por defecto en la mayor\u00eda de las implementaciones.\n\nGu\u00eda de detecci\u00f3n:\n\n* Inspeccionar los metadatos de la tabla metastore / Hive en busca de tablas Avro cuya avro.schema.url utilice esquemas inesperados como http, https, file o ftp, o apunte a direcciones de metadatos link-local / en la nube (por ejemplo, 169.254.169.254) u otros hosts internos.\n* Revisar los registros de HiveServer2 y Metastore en torno a CREATE/ALTER TABLE y las consultas contra tablas Avro en busca de fallos en la resoluci\u00f3n de esquemas o de obtenciones salientes de avro.schema.url.\n* Correlacionar la actividad CREATE TABLE / ALTER TABLE que establece avro.schema.url con la actividad SELECT posterior en la misma tabla, especialmente cuando el destino de la URL es inusual para la distribuci\u00f3n de esquemas.\n* En implementaciones en la nube, verificar los registros de flujo de instancias / VPC y los registros de acceso al servicio de metadatos en busca de solicitudes inesperadas de identidades de host de Hive poco despu\u00e9s de la actividad DDL o de consulta de Avro."}], "lastModified": "2026-09-28T23:10:00.143", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:apache:hive:4.2.0:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "5EBBABEC-E6AB-4106-8445-80964A219DB5"}], "operator": "OR"}]}], "sourceIdentifier": "security@apache.org"}