Secuno
ENNL
Book demo

CVE-2026-41041

Apache Gravitino vulnerability

9.1 CRITICALEPSS 0.60%
  1. Published13 Jul 2026

Description

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 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Apache Gravitino≥ 1.0.0 < 1.2.1

Remediation

Fixed in
Apache Gravitino≥ 1.2.1

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-765049.8
A vulnerability in the API session-based authentication management of Cisco Catalyst…
CVE-2026-153718.1
Velociraptor's web GUI allows specifying a custom type for columns in tables. The URL…
CVE-2026-590839.1
Improper Handling of URL Encoding (Hex Encoding) vulnerability in Apache Tomcat's…
CVE-2026-220378.4
The @fastify/express plugin adds full Express compatibility to Fastify. A security…
CVE-2026-220318.4
@fastify/middie is the plugin that adds middleware support on steroids to Fastify. A…

Frequently asked

Is CVE-2026-41041 being actively exploited?

CVE-2026-41041 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.60%.

How severe is CVE-2026-41041?

CVE-2026-41041 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.60% probability of exploitation.

Which products are affected by CVE-2026-41041?

Affected products include Apache Gravitino.

How do I fix CVE-2026-41041?

Upgrade affected software to a fixed version, for example Apache Gravitino 1.2.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-41041 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.