CVE-2026-41041

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-13. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
EPSS
44.7%
KEV
Not listed

Published

July 13, 2026

Last Modified

July 13, 2026

Advisory Details (2)

Auto-updated Jul 13, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-41041: Apache Gravitino: URL path injection via unencoded user-supplied identifiers in MCP REST client f-string URL construction, enabling path traversal to unintended API endpoints.

http://www.openwall.com/lists/oss-security/2026/07/13/1

Vendor Advisories for CVE-2026-41041(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
apache-gravitino1.0.0 ... 1.2.1rc2 (28 versions)1.2.1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:24 UTCEPSS rescore
  3. 2026-07-20 17:08 UTCEPSS rescore
  4. 2026-07-19 14:31 UTCEPSS rescore
  5. 2026-07-19 02:29 UTCEPSS rescore
  6. 2026-07-18 10:04 UTCEPSS rescore
  7. 2026-07-17 02:53 UTCGHSA enrichment
  8. 2026-07-16 22:30 UTCGHSA enrichment
  9. 2026-07-16 18:06 UTCGHSA enrichment
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-16 13:42 UTCGHSA enrichment
  12. 2026-07-16 09:20 UTCEG score recompute 9.10
  13. 2026-07-16 09:20 UTCGHSA enrichment
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-13 22:30 UTCEPSS rescore
  18. 2026-07-13 17:12 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  19. 2026-07-13 12:22 UTCNVD update
  20. 2026-07-13 11:57 UTCMITRE cvelistV5
  21. 2026-07-13 10:22 UTCNVD update
  22. 2026-07-13 09:54 UTCEG score recompute
  23. 2026-07-13 09:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-41041?
CVE-2026-41041 is a critical vulnerability published on July 13, 2026. 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.
When was CVE-2026-41041 disclosed?
CVE-2026-41041 was first published in the National Vulnerability Database on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41041 actively exploited?
CVE-2026-41041 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 44.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41041?
CVE-2026-41041 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-41041?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41041, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41041

Explore →

Is Your Infrastructure Affected by CVE-2026-41041?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.