Cyber Resilience

CVE-2026-41041

Apache Gravitino 1.0.0 – 1.2.1

Published
13 July 2026
Modified
13 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 9.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.0060 47th percentile
Risk Priority 68 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-41041 is a critical-severity Hex Encoding (CWE-177) vulnerability in Apache Gravitino. Its CVSS base score is 9.1 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 47th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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.

CWE(s)
CWE-177

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-49876Same product: Apache Gravitino
CVE-2025-53648Same product: Apache Gravitino
CVE-2026-59083Same vendor: Apache
CVE-2026-40948Same vendor: Apache
CVE-2024-46911Same vendor: Apache
CVE-2026-55957Same vendor: Apache
CVE-2024-36104Same vendor: Apache
CVE-2024-53678Same vendor: Apache
CVE-2024-45693Same vendor: Apache
CVE-2024-27439Same vendor: Apache

Affected Assets

apache
gravitino
1.0.0 — 1.2.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.2

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match

Proper input validation requires decoding and checking URL-encoded data before use, directly stopping the weakness from being exploitable.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
prevents

Secure SDLC practices directly require correct URL-encoding/decoding and input validation during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC processes include validation steps that reduce CWE-177, yet the control is broader than this single weakness.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for input validation and canonicalization, directly preventing improper URL decoding.

A.8.28 Secure coding partial match
prevents

Secure coding standards mandate proper handling and decoding of encoded inputs, eliminating CWE-177.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing in development catches URL-decoding flaws before release, but does not itself define coding rules.

References