SSRF (Server-Side Request Forgery) in apache-gravitino (CVE-2026-49876)
Summary
SSRF in apache-gravitino (CVE-2026-49876). Confidential information can be exposed externally. Mitigation: upgrade to 1.3.0 or later.
Original description
The description as published by the source.
Authenticated SSRF in Gravitino JobManager allows server-side HTTP requests to internal network and cloud metadata endpoints via unvalidated job template URIs. A vulnerability in Apache Gravitino.
This issue affects Apache Gravitino: from 1.0.0 through 1.2.1.
Users are recommended to upgrade to version 1.3.0, which fixes the issue.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49876 has been found in apache-gravitino.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade apache-gravitino to 1.3.0 or later.
If unsure, ask your IT team or search "apache-gravitino CVE-2026-49876" on the vendor's site.
CVE-2026-49876 (apache-gravitino) — CWE-918 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.3.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in apache-gravitino.
Check the vendor advisory for the affected versions of apache-gravitino.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 1.3.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'apache-gravitino' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'apache-gravitino' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
apache-gravitinoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade apache-gravitino to 1.3.0ステージング環境で 1.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory lists.apache.org
- advisory openwall.com
- web nvd.nist.gov
- web github.com