WhatBrokeToday
GTA 6FAQ
Apache

Apache Griffin Web Service Missing Authentication Vulnerability

high

Is it fixed? Not yet.

Ongoing since Nov 16, 10:16 UTC. First reported Nov 16, 10:16 UTC.

What happened

Apache Griffin Web Service contains a missing authentication vulnerability in its REST API, which exposes sensitive endpoints such as job submission when a Livy/Spark backend is configured. The project is retired and unsupported, and all versions are affected.

What caused it?

The REST API does not have any authentication, leaving sensitive endpoints unprotected.

Workaround available

The API must be properly secured on the network level.

Reported inCVEevidence [1]

Timeline

  1. Investigating(done)
  2. Workaround available(current)
  3. Resolved(upcoming)
  1. First report on security advisory

    Apache Griffin Web Service: CVE-2026-128841 (High)

    Source
  2. Workaround discovered

    Workaround reported: The API must be properly secured on the network level.

    Source
  3. Status changed

    Status changed: new → workaround_available (workaround reported in source signals).

Evidence

1 report · 1 CVEShow
  1. [1]
    CVE First report
    Apache Griffin Web Service: CVE-2026-128841 (High)(opens security advisory in a new tab)

    High severity. ** 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,…

    by Tenable 0upvotes 0comments

FAQ

What happened in the Apache issue?

Apache Griffin Web Service contains a missing authentication vulnerability in its REST API, which exposes sensitive endpoints such as job submission when a Livy/Spark backend is configured. The project is retired and unsupported, and all versions are affected.

What is affected by the Apache issue?

Apache (versions: all versions). Also affected at the same time: Linux.

When did the Apache issue start and end?

It started Nov 16, 10:16 UTC and is still ongoing (2 d 18 h so far). This page updates as it develops.

How do I get alerts for Apache?

Subscribe to the Apache RSS feed for every new Apache incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Apache is down. Apache feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.