Cyber Resilience

CVE-2026-41041

Apache Gravitino 1.0.0 – 1.2.1

Published
13 July 2026
Modified
13 July 2026
Patch / 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.0047 38th percentile
Risk Priority 70 floored blend · peak EPSS

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 38th 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) and SC-7 (Boundary Protection) — 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)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

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.
Why these techniques?

URL path injection via improper URL encoding (CWE-177) in a web-exposed service directly enables exploitation of public-facing applications.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-49876Same product: Apache Gravitino
CVE-2025-53648Same product: Apache Gravitino
CVE-2026-59083Same vendor: Apache
CVE-2025-55754Same vendor: Apache
CVE-2026-49268Same vendor: Apache
CVE-2026-33454Same vendor: Apache
CVE-2026-50630Same vendor: Apache
CVE-2026-44417Same vendor: Apache
CVE-2026-32228Same vendor: Apache
CVE-2026-49328Same vendor: Apache

Affected Assets

apache
gravitino
1.0.0 — 1.2.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SC-7 Boundary Protection
Detect
Catch it (NIST detect / respond)
  • SC-7 Boundary Protection
  • SI-2 Flaw Remediation
Harden
Shrink the surface (DISA STIG)

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

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires validation and encoding of untrusted user-supplied identifiers before they are placed into URL paths, blocking the CWE-177 injection.

preventdetect

Boundary-protection devices (WAFs, API gateways) can inspect and reject malformed or path-injected requests targeting Gravitino endpoints.

respondrecover

Mandates timely application of the vendor patch that corrects the missing URL encoding logic in versions before 1.2.1.

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

detects

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

prevents

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

prevents

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

prevents

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

References