CVE-2026-128841

waiting for further signalsZero needs more public information before it can validate it.

GHSA-fm47-2v94-rf8p ↗EUVD-2026-126192 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Apache Software Foundation Apache Griffin Web Service <= *
CWE-306 Missing Authentication for Critical Function
ETK-2026-4574Zero's internal tracking ID, independent of the CVE number., permanent identifier
2d 11h 11msince last run
1h 26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h51m
0
+4h
+6h
+8h
+10h
+12h

description

All versions of Apache Griffin Web Service expose REST API endpoints without authentication. An attacker able to reach the service can access sensitive functions, including job submission when the deployment uses a Livy/Spark backend.

mitigation

Replace Griffin Web Service with a supported alternative. Until it is removed, restrict network access to trusted users and systems only.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.22%12th percentile
agent run time
1h 26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-16 09:03Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-16 09:03Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-128841

{
  "etk_id": "ETK-2026-4574",
  "cve_id": "CVE-2026-128841",
  "display_id": "CVE-2026-128841",
  "ghsa_id": "GHSA-fm47-2v94-rf8p",
  "euvd_id": "EUVD-2026-126192",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated REST API access in Griffin Web Service",
  "summary": "All versions of Apache Griffin Web Service expose REST API endpoints without authentication. An attacker able to reach the service can access sensitive functions, including job submission when the deployment uses a Livy/Spark backend.",
  "mitigation": "Replace Griffin Web Service with a supported alternative. Until it is removed, restrict network access to trusted users and systems only.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Griffin Web Service",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= *"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "org.apache.griffin:service",
      "purl": null
    }
  ],
  "cwes": [
    306
  ],
  "cvss_score": 7.5,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.0022,
  "epss_percentile": 0.1243,
  "epss_asof": "2026-11-17",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 86.31240296666667,
  "t0_at": "2026-11-16T09:03:45.099000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-16T09:03:45.099000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-16T09:03:45.099000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-128841"
    }
  }
}

published 2026-11-16 09:28Z
last change 2026-11-18 21:43Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.