dbcve.org
GravitinoApplication · Apache

CVE-2026-49876

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-13
Fix available
A fix is available. Upgrade to 1.3.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authenticated SSRF vulnerability in Apache Gravitino's JobManager allows attackers with valid credentials to inject malicious URIs in job templates, causing the server to make HTTP requests to internal network resources and cloud metadata endpoints (e.g., AWS EC2 metadata service at 169.254.169.254). The lack of URI validation on job template inputs enables internal reconnaissance and potential credential theft.

MitigationUpgrade to Apache Gravitino 1.3.0 or later. If immediate upgrade is not feasible, implement network-level controls to block server egress to internal IP ranges and metadata endpoints, and add application-layer URI allowlist validation for job template inputs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GravitinoApplication
Affected:>= 1.0.0, < 1.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Gravitino installation and version
    Locate the Gravitino installation directory or process, then check the version file or startup logs for the exact version number. Compare against the affected range: >= 1.0.0, < 1.3.0
    Affected if The installed version falls within >= 1.0.0 and < 1.3.0
  2. Confirm JobManager module is in use
    Check if the Gravitino JobManager service is running or enabled. This may be visible in the service process list, configuration files, or deployment manifests
    Affected if JobManager is running and accessible to authenticated users
  3. Verify job template creation capability
    Using valid credentials, attempt to access the job template creation interface or API endpoint in Gravitino. Check if the template input accepts URI/URL fields
    Affected if Authenticated users can create or modify job templates with URI/URL input fields
  4. Test URI validation on job template inputs
    Submit a test job template with an internal URI such as http://169.254.169.254/latest/meta-data/ (AWS metadata endpoint) or http://127.0.0.1 as the URI parameter. Observe if the server accepts or processes the request without validation errors
    Affected if The server accepts and attempts to process requests to internal network addresses or metadata endpoints without rejecting or validating the URI

You are affected if Apache Gravitino version 1.0.0 through 1.2.x is running with JobManager accessible to authenticated users, and job template inputs accept URIs without validating against internal network addresses or metadata endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.3.0 or later
Fixed in 1.3.0
Interim mitigation

Upgrade to Apache Gravitino 1.3.0 or later. If immediate upgrade is not feasible, implement network-level controls to block server egress to internal IP ranges and metadata endpoints, and add application-layer URI allowlist validation for job template inputs.

Recommended fix High confidence

1.3.0

  1. Back up your current Gravitino installation, configuration, and any persistent data
  2. Review the Apache Gravitino 1.3.0 release notes for any known breaking changes or migration requirements
  3. Stop the Gravitino service
  4. Upgrade Gravitino from your current version (< 1.3.0) to version 1.3.0
  5. Start the Gravitino service and verify it runs without errors
  6. Confirm the SSRF vulnerability is resolved by testing that job templates cannot make arbitrary HTTP requests to internal network or cloud metadata endpoints
Caveat Check 1.3.0 release notes for any breaking changes; upgrade carries standard migration risk

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gravitino Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49876 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49876 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data