# CVE-2026-93737: Azkaban through 4.0.0 Authorization Bypass via ScheduleServlet

> Authenticated users can bypass project permission checks to read sensitive schedule configurations of any project in Azkaban.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-wcv9-64xq-42pp

## What is CVE-2026-93737?

CVE-2026-93737 is a high-severity missing authorization vulnerability in azkaban, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Azkaban through 4.0.0 omits project permission checks in the ScheduleServlet fetchSchedule action, allowing authenticated users to read any project's schedule configuration. Attackers can supply arbitrary project and flow identifiers to retrieve sensitive schedule details including execution times, cron expressions, flow parameters, and notification email lists without proper authorization.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-93737?


## How do I fix CVE-2026-93737?

No fix has been published for CVE-2026-93737 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93737 being exploited?

There is no known exploitation of CVE-2026-93737 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93737 and fix it if it is affected.

What it is: CVE-2026-93737 is a high-severity missing authorization vulnerability in azkaban, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93737 in the wild and no public exploit code.

Affected product: azkaban. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93737/ (Markdown: https://insights.sbomify.com/CVE-2026-93737/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93737
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93737
- OSV: https://osv.dev/vulnerability/CVE-2026-93737

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93737/
Summaries are generated and may contain mistakes; the official description above is the record.