Skip to main content
Menu
CVEs

CVE

Apache Service missing authentication in REST API

CVE-2026-128841EUVD-2026-126192GHSA-FM47-2V94-RF8P

Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported
Published
Last modified
Reference
Last checked
0.21% · 11th percentile
15/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

The Apache Griffin Web Service has a REST API that requires no authentication, so anyone who can reach it can use sensitive endpoints, including job submission when a Livy/Spark backend is configured. The vendor says the API must be secured at the network level, and the project is retired, so no fix is planned.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

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.

cve.now Index

15Pcve.now Index 15 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach10/20Affects Maven packages
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 37 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-128841 (Apache Griffin Web Service: REST API is unauthenticated), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-128841 (entry last updated 2026-11-16):
Affected:
- Maven package org.apache.griffin:service: all versions
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-128841 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128841 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread.html/9fls3018wcgl0k0srsfofvlncgskb8jh
- http://www.openwall.com/lists/oss-security/2026/11/16/3
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-128841
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128841"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Record last updated

Affected versions

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Write-ups · 1

Establishes: Technical detail and context.

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-128841

Is CVE-2026-128841 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-128841?

org.apache.griffin:service (Maven): all versions.Source: cve.now feed data