# CVE-2026-41041: Apache Gravitino URL path injection via unencoded identifiers

Source: https://junglewise.ai/threats/cve-2026-41041-apache-gravitino-url-path-injection-via-unencoded-identifiers  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-13. Updated: 2026-07-13  
License: CC BY 4.0 with a link back

CVE-2026-41041 · Severity: low · CVSS 3.1 · Published 2026-07-13

Apache Gravitino, a high-performance metadata lake, is vulnerable to a security flaw where user-provided identifiers are not properly cleaned before being used in web addresses. This could allow an attacker to manipulate application requests, potentially leading to unauthorized access to data or unintended system behavior. Organizations should update to version 1.2.1 to resolve this issue.

Technologies: [Apache Software Foundation Gravitino](https://junglewise.ai/threats/technologies/gravitino). Vendors: [Apache Software Foundation](https://junglewise.ai/threats/vendors/apache-software-foundation), [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2026-41041 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-41041 being exploited in the wild.

**How severe is CVE-2026-41041?** Low severity, with a CVSS score of 3.1, published 13 July 2026.

**Which products and versions are affected?** Apache Software Foundation Gravitino 1.0.0 to 1.2.0; apache-gravitino (PyPI) ECOSYSTEM:introduced=1.0.0,fixed=1.2.1.

**Is there a fix for CVE-2026-41041?** Yes. apache-gravitino (PyPI): upgrade to 1.2.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-41041 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-41041?** Check whether you run Apache Software Foundation Gravitino or apache-gravitino (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- apache-gravitino (PyPI): upgrade to 1.2.1 or later

  ```sh
  pip install "apache-gravitino>=1.2.1"
  ```


## Technical details

A URL path injection vulnerability exists in Apache Gravitino due to improper handling of URL encoding (CWE-177). The application fails to adequately encode user-supplied identifiers before incorporating them into URL paths. An attacker can exploit this by providing specially crafted identifiers containing path traversal or control characters, potentially allowing them to influence internal API calls or access unintended resources. This issue affects versions 1.0.0 through 1.2.0 and is resolved in version 1.2.1.

## Affected products

- Apache Gravitino 1.0.0 to 1.2.0

## Identifiers

- CVE-2026-41041
- PYSEC-2026-3441

## Timeline

- 2026-07-13: disclosed
- 2026-07-13: advisory

## References

- [https://lists.apache.org/thread/4dnwg1qzb2yns1fkfmq0z45vmwyzytgz](https://lists.apache.org/thread/4dnwg1qzb2yns1fkfmq0z45vmwyzytgz)

## Related threats

- [Apache Gravitino SSRF in JobManager via job template URIs](https://junglewise.ai/threats/cve-2026-49876-apache-gravitino-ssrf-in-jobmanager-via-job-template-uris)
- [Apache Gravitino RCE via malicious H2 JDBC URL in testConnection API](https://junglewise.ai/threats/cve-2026-41042-apache-gravitino-rce-via-malicious-h2-jdbc-url-in-testconnection)
- [Apache Gravitino SQL injection in UI](https://junglewise.ai/threats/cve-2025-53648-apache-gravitino-sql-injection-in-ui)