dbcve.org
GravitinoApplication · Apache

CVE-2026-41041

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-13
Fix available
A fix is available. Upgrade to 1.2.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
URL path injection via unencoded user-supplied identifiers vulnerability in Apache Gravitino. This issue affects Apache Gravitino: from 1.0.0 before 1.2.1. Users are recommended to upgrade to version 1.2.1, 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

A URL path injection vulnerability exists in Apache Gravitino versions 1.0.0 through 1.2.0 where user-supplied identifiers are not properly encoded before being used in URL paths. This allows attackers to manipulate URL paths and potentially access unauthorized resources or execute path traversal attacks.

MitigationUpgrade Apache Gravitino to version 1.2.1 or later to remediate this vulnerability.

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.2.1

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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. Confirm Apache Gravitino is installed
    Check for Gravitino processes running on the system using process inspection tools or check for Gravitino installation directories
    Affected if Gravitino is running or installed on the system
  2. Identify installed Gravitino version
    Locate the Gravitino version information in the installation directory or by using the Gravitino command line version flag if available
    Affected if The installed version is 1.0.0 through 1.2.0 inclusive
  3. Verify web server configuration
    Inspect Gravitino configuration files for HTTP/HTTPS server settings to determine if the REST API is enabled
    Affected if The REST API or web server is enabled and accessible
  4. Check URL handling in logs
    Review Gravitino server logs for any unusual or malformed URL path patterns that may indicate injection attempts or path traversal behavior
    Affected if Unusual URL path patterns appear in logs or request patterns suggest path manipulation
  5. Identify exposed API endpoints
    Examine the Gravitino configuration to determine which API endpoints are exposed, focusing on endpoints that accept user-supplied identifiers in URL paths
    Affected if API endpoints accepting user identifiers in URL paths are publicly or internally accessible

You are affected if Apache Gravitino version 1.0.0 through 1.2.0 is running with the web REST API exposed and URL endpoints that accept user-supplied identifiers are accessible.

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.2.1 or later
Fixed in 1.2.1
Interim mitigation

Upgrade Apache Gravitino to version 1.2.1 or later to remediate this vulnerability.

Recommended fix High confidence

1.2.1

  1. 1. Back up your current Gravitino configuration and data directories.
  2. 2. Stop the running Gravitino service.
  3. 3. Download Apache Gravitino version 1.2.1 from the official Apache download mirrors or GitHub releases.
  4. 4. Replace the existing Gravitino installation with the new version 1.2.1.
  5. 5. Restore your backed-up configuration files to the new installation.
  6. 6. Start the Gravitino service and verify it runs successfully.
  7. 7. Test that the URL path injection vulnerability is remediated by validating that user-supplied identifiers in URLs are properly encoded.

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

Fix this in Gravitino Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41041 — 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-41041 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