CVE-2026-55976: Software Security Vulnerability Vulnerability
CRITICALCVE-2026-55976 is a CRITICAL (CVSS 9.1) security vulnerability vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Software libraries in the Maven ecosystem. The weakness occurs when the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination.. Remediation is available in the latest vendor maintenance releases.
CVE-2026-55976 at a Glance
Security Impact
CVSS: 9.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).
How to Fix CVE-2026-55976
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.
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:treeHow to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-55976, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:treeAnalyze 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-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. 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
References
Frequently Asked Questions
What is CVE-2026-55976?
Which Software versions are affected?
What version fixes CVE-2026-55976?
What is the CVSS score of CVE-2026-55976?
What CWE is associated with CVE-2026-55976?
How can I check Maven dependencies for CVE-2026-55976?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-gp8m-92x3-q87g",
"modified" : "2026-08-26T21:31:33Z",
"published" : "2026-08-25T12:31:23Z",
"aliases" : [ "CVE-2026-55976" ],
"details" : "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 table 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 in 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 uses 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 with 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.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N"
} ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-55976"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/hive/commit/45049202df35cea382616624de3fe8d252aa2d00"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/hive"
}, {
"type" : "WEB",
"url" : "https://issues.apache.org/jira/browse/HIVE-29671"
}, {
"type" : "WEB",
"url" : "https://lists.apache.org/thread/6d56mk501fp4f8cb5wvrpj2jwd9knt05"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-918" ],
"severity" : "CRITICAL",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-25T11:16:53Z"
}
}