Skip to main content

Apache Gravitino CVE-2026-49876

| EUVDEUVD-2026-43323 MEDIUM
Server-Side Request Forgery (SSRF) (CWE-918)
2026-07-13
6.5
CVSS 3.1 · Vendor
Share

Severity by source

Vendor (CNA) PRIMARY
6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
vuln.today AI
7.7 HIGH

Network-reachable API, low complexity; PR:L reflects mandatory authentication; S:C and C:H capture SSRF pivot to cloud metadata credential disclosure; no integrity or availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N

Primary rating from Vendor (CNA).

CVSS VectorVendor

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

2
CVSS changed
Jul 13, 2026 - 15:22 NVD
6.5 (MEDIUM)
Analysis Generated
Jul 13, 2026 - 04:16 vuln.today

Description PRE-NVD

Disclosed via oss-security. NVD scoring and full description are pending.

AnalysisAI

Authenticated SSRF in Apache Gravitino's JobManager component (versions 1.0.0 through 1.2.1) enables authenticated users to coerce the server into making arbitrary outbound HTTP requests to internal network hosts and cloud instance metadata services (e.g., AWS IMDS at 169.254.169.254, GCP metadata endpoints) by supplying unvalidated URIs within job templates. In cloud-hosted deployments this is a credential-theft primitive: metadata service access can yield IAM role credentials with blast radius extending well beyond the Gravitino service itself. No public exploit or CISA KEV listing has been identified at time of analysis; vendor labels severity as moderate, though cloud-metadata reachability elevates real-world impact above that rating in typical deployment contexts.

Technical ContextAI

Apache Gravitino (org.apache.gravitino:gravitino-core) is a federated metadata lake and data-catalog platform designed to unify metadata management across heterogeneous data sources - relational databases, file stores, event streams - and multi-engine query environments (Trino, Spark, Flink). The JobManager component accepts job template definitions that include URI fields used to drive server-side HTTP interactions; these URIs are passed to an outbound HTTP client without allowlist validation or scheme restriction. The root cause is a classic Server-Side Request Forgery (CWE-918): user-controlled input reaches an internal HTTP dispatcher that is trusted by co-located services such as cloud metadata endpoints. CPE: cpe:2.3:a:apache:gravitino:*:*:*:*:*:*:*:* for the range 1.0.0 through 1.2.1. No CWE was formally assigned in the advisory, but the description maps directly to CWE-918 (Server-Side Request Forgery). Cloud metadata services (operating on link-local address 169.254.169.254 or equivalent) are a particularly high-value target because they are accessible from the host without any additional credentials and return instance identity documents and ephemeral IAM credentials.

RemediationAI

The primary remediation is upgrading Apache Gravitino to version 1.3.0, which is confirmed by the Apache advisory to contain the fix for this issue. Refer to https://gravitino.apache.org for release artifacts and https://seclists.org/oss-sec/2026/q3/123 for the original disclosure. If an immediate upgrade is not feasible, compensating controls should focus on restricting what the Gravitino server process can reach outbound: configure network-level egress filtering (firewall or security-group rules) to block the Gravitino host from initiating connections to RFC-1918 address ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) and the link-local range 169.254.0.0/16 used by cloud metadata services. Note that blocking 169.254.169.254 removes access to instance metadata, which may disrupt IAM role credential refresh if the Gravitino service itself relies on instance profiles - evaluate this side effect before applying. Additionally, restrict the JobManager feature to a minimum set of trusted users via Gravitino's access-control layer to reduce the population of accounts that can submit job templates. These workarounds reduce but do not eliminate SSRF risk, as internal services on non-standard ports may still be reachable. Upgrade to 1.3.0 remains the only complete fix.

Share

CVE-2026-49876 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy