CVE-2026-49845

{"id": "CVE-2026-49845", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-49845", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-08-25T00:00:00+00:00"}}], "cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 9.8, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security@apache.org", "affectedData": [{"vendor": "Apache Software Foundation", "product": "Apache Hive", "versions": [{"status": "affected", "version": "4.0.0", "versionType": "semver", "lessThanOrEqual": "4.2.0"}], "packageName": "org.apache.hive:hive-standalone-metastore", "collectionURL": "https://repo.maven.apache.org/maven2", "defaultStatus": "unaffected"}]}], "published": "2026-08-25T11:16:53.410", "references": [{"url": "https://github.com/apache/hive", "tags": ["Product"], "source": "security@apache.org"}, {"url": "https://github.com/apache/hive/commit/ca64f08a8e43db9845b47d5fa2e96f7fdea7288e", "tags": ["Patch"], "source": "security@apache.org"}, {"url": "https://issues.apache.org/jira/browse/HIVE-29622", "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-94"}]}], "descriptions": [{"lang": "en", "value": "SQL injection in Hive Metastore direct SQL partition-name resolution in Apache Hive before 4.2.1 on all platforms allows authenticated users with access to Hive Metastore APIs to read, modify, or affect unintended partition metadata (including statistics updates, truncation targets, and file-metadata cache operations) via crafted partition names in metastore RPC requests when direct SQL is enabled (the default). Users are recommended to upgrade to version 4.2.1, which fixes this issue.\n\nDetails about the issue:\nSeveral Hive Metastore RPCs resolve partitions by full partition name (PART_NAME) through direct-SQL helpers. In those paths, client-supplied partition names are embedded into SQL using string concatenation (DirectSqlUpdatePart.quoteString() \u2192 '...') instead of bind parameters.\u00a0A partition name containing a single quote (and crafted SQL) can alter the generated WHERE clause so that lookups intended for one partition match additional rows. That can affect reads, stats updates, truncate targets, metadata-cache targets, and related operations when metastore.try.direct.sql is enabled (default: true).\u00a0An authenticated or network-trusted caller with the ability to invoke Hive Metastore partition-name APIs against a target table (directly or via Hive/other clients), when direct SQL is enabled can perform this attack. Also, the impact is mainly within table & partition targeting (read/update/truncate/drop/cache the wrong partitions in a table they can reference), not arbitrary cross-database access via this bug alone."}, {"lang": "es", "value": "La inyecci\u00f3n SQL en la resoluci\u00f3n de nombres de partici\u00f3n SQL directa de Hive Metastore en Apache Hive anterior a 4.2.1 en todas las plataformas permite a usuarios autenticados con acceso a las API de Hive Metastore leer, modificar o afectar metadatos de partici\u00f3n no deseados (incluyendo actualizaciones de estad\u00edsticas, objetivos de truncamiento y operaciones de cach\u00e9 de metadatos de archivos) a trav\u00e9s de nombres de partici\u00f3n manipulados en solicitudes RPC de metastore cuando el SQL directo est\u00e1 habilitado (el valor predeterminado). Se recomienda a los usuarios actualizar a la versi\u00f3n 4.2.1, que corrige este problema.\n\nDetalles sobre el problema:\nVarias RPC de Hive Metastore resuelven particiones por nombre de partici\u00f3n completo (PART_NAME) a trav\u00e9s de ayudantes de SQL directo. En esas rutas, los nombres de partici\u00f3n proporcionados por el cliente se incrustan en SQL usando concatenaci\u00f3n de cadenas (DirectSqlUpdatePart.quoteString() ? '...') en lugar de par\u00e1metros de enlace. Un nombre de partici\u00f3n que contiene una comilla simple (y SQL manipulado) puede alterar la cl\u00e1usula WHERE generada de modo que las b\u00fasquedas destinadas a una partici\u00f3n coincidan con filas adicionales. Eso puede afectar lecturas, actualizaciones de estad\u00edsticas, objetivos de truncamiento, objetivos de cach\u00e9 de metadatos y operaciones relacionadas cuando metastore.try.direct.sql est\u00e1 habilitado (predeterminado: true). Un llamador autenticado o de confianza de red con la capacidad de invocar las API de nombres de partici\u00f3n de Hive Metastore contra una tabla objetivo (directamente o a trav\u00e9s de Hive/otros clientes), cuando el SQL directo est\u00e1 habilitado puede realizar este ataque. Adem\u00e1s, el impacto es principalmente dentro de la orientaci\u00f3n de tabla y partici\u00f3n (leer/actualizar/truncar/eliminar/almacenar en cach\u00e9 las particiones incorrectas en una tabla a la que pueden hacer referencia), no acceso arbitrario entre bases de datos a trav\u00e9s de este error solamente."}], "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"}