CVE-2026-128841 in Griffin Web Serviceinfo

Summary

by MITRE • 11/16/2026

** UNSUPPORTED WHEN ASSIGNED ** Missing authentication for critical function vulnerability in Apache Griffin Web Service. The REST API does not have any authentication. This includes sensitive endpoints, such as job submission when a Livy/Spark backend is configured. The API must be properly secured on the network level, and this fact was arguably not documented as clearly as it could have.



This issue affects Apache Griffin Web Service: all versions.



As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative or restrict access to the instance to trusted users.



NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/16/2026

The Apache Griffin Web Service suffers from a critical missing authentication flaw within its REST API architecture, specifically affecting all versions of the software prior to its retirement. This vulnerability stems from an incomplete implementation of access control mechanisms for sensitive operational endpoints. In particular, functions that facilitate job submission when configured with a Livy or Spark backend are exposed without any form of user verification or credential validation. The absence of authentication allows unauthenticated actors to interact directly with these high-privilege interfaces, bypassing the intended security boundaries of the application layer entirely.

From a technical perspective, this represents a classic case of broken access control where the server fails to enforce identity checks before executing state-changing operations. When an attacker interacts with the job submission endpoint, they can trigger computational tasks on the underlying Spark or Livy infrastructure without authorization. This lack of authentication means that any entity capable of reaching the network port hosting the Apache Griffin service can initiate resource-intensive jobs, modify system configurations, or potentially execute arbitrary code depending on how the backend interprets and processes these requests. The vulnerability is exacerbated by insufficient documentation regarding the necessity for external network-level security controls, leading administrators to assume default protections were in place when they were not.

The operational impact of this vulnerability is severe due to its potential for denial-of-service attacks and unauthorized resource consumption. An attacker can submit malicious or excessively heavy jobs that consume significant CPU, memory, and storage resources on the backend cluster, effectively rendering the service unavailable for legitimate users. Furthermore, if the underlying Spark environment allows for code execution through job submissions, this could lead to remote code execution (RCE) within the context of the user running the Apache Griffin process. This poses a risk not only to the immediate infrastructure but also to any connected data stores or downstream systems that the backend cluster has access to, potentially leading to data exfiltration or corruption.

In terms of industry standards and threat modeling, this vulnerability aligns with CWE-287: Improper Authentication, as the system fails to verify the identity of users attempting to perform privileged actions. It also maps closely to MITRE ATT&CK technique T1059 Command and Scripting Interpreter if used for RCE, or T1496 Resource Hijacking in the context of denial-of-service via resource exhaustion. The lack of input validation on job parameters further compounds the risk, potentially inviting CWE-20: Improper Input Validation vulnerabilities that could be chained with the authentication bypass to achieve more complex attack vectors such as server-side request forgery or injection attacks against internal services.

Given that Apache Griffin is a retired project and no patch will be released by the maintainers, mitigation strategies must focus on external defense-in-depth measures rather than software updates. The primary recommendation is to restrict network-level access to the service using firewalls, security groups, or reverse proxies configured with strict IP whitelisting. Access should only be permitted from trusted internal networks and specific administrative workstations that require interaction with the job submission features. Additionally, implementing mutual TLS (mTLS) at the load balancer or ingress controller level can provide an additional layer of authentication before requests reach the application server. Administrators are strongly advised to migrate away from Apache Griffin as soon as possible, adopting actively maintained alternatives for data quality monitoring and analytics that include robust, up-to-date security controls including proper authentication and authorization frameworks.

Responsible

Apache

Reservation

11/13/2026

Disclosure

11/16/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!