/

CVE-2026-93559

Severity:

HIGH RISK

(7.3)

Missing Authentication (CWE-306) in Jellyfish FastAPI

CVE-2026-93559

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-287, CWE-306

Impact:

Unauthorized access to protected application functionality

Severity:

HIGH RISK

(7.3)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Jellyfish AI Short Drama Studio contains a missing-authentication vulnerability in a FastAPI-related component. A remote attacker may reach affected functionality without first proving their identity, which could expose protected operations or data depending on deployment and endpoint behavior.

Affected context

The issue affects Jellyfish AI Short Drama Studio releases that include the affected logic in backend/app/dependencies.py. Risk is present when a remotely reachable FastAPI route relies on an authentication dependency that is absent, incorrectly applied, or not enforced for the relevant operation. The practical impact depends on which endpoints are exposed and what permissions those endpoints provide.

Exploit preconditions

  • Attack surface: A remotely reachable FastAPI application endpoint
  • Required access: Network connectivity to the affected service; valid credentials may not be required
  • Trigger point: A request to functionality whose authentication dependency is missing or ineffective
  • Why exploitation is possible: The application may process the request without establishing the caller's identity before allowing access to protected behavior

Why this happens

The underlying bug is an authentication-enforcement failure in the web application's dependency configuration. A route or critical operation can be exposed without a mandatory authentication check, allowing requests to proceed as though the caller had been verified. This maps primarily to CWE-306: Missing Authentication for Critical Function, with CWE-287: Improper Authentication also relevant when authentication exists but is not correctly applied or enforced.

Potential impact

  • An unauthenticated user may access functionality intended for authenticated users
  • Attackers could retrieve or modify application data if affected endpoints permit those actions
  • Unauthorized requests may trigger resource-intensive or administrative operations
  • The application could experience data exposure, integrity loss, or service disruption

General mitigation guidance

Mitigation generally focuses on making authentication mandatory for every protected operation and reducing reliance on implicit route configuration.

Common defensive patterns include:

  • Applying centralized authentication dependencies to protected routers or endpoint groups
  • Enforcing authorization checks after authentication, using least-privilege roles
  • Failing closed when authentication configuration is missing, invalid, or unavailable
  • Separating public endpoints from protected endpoints through explicit policy
  • Treating client-supplied identity, role, and permission values as untrusted
  • Adding automated tests that verify unauthenticated requests cannot reach protected functionality
  • Limiting service exposure and placing administrative interfaces behind appropriate network controls

How teams detect issues like this

Organizations can look for authentication gaps through:

  • Static analysis rules that identify routes lacking required authentication dependencies
  • Code review checks comparing route declarations with the application's endpoint protection policy
  • Integration tests for anonymous, authenticated, and unauthorized requests
  • API inventory reviews that identify externally reachable administrative or data-changing operations
  • Runtime monitoring for repeated anonymous requests to protected paths and unexpected successful responses
  • Policy enforcement requiring explicit security annotations or dependency declarations for sensitive routes

Automated code review and API security testing tools can help identify routes whose protection differs from established policy.

Sources

SourceLink
github.comgithub.com/Forget-C/Jellyfish/issues/37
vuldb.comvuldb.com/cve/CVE-2026-93559
vuldb.comvuldb.com/submit/943920
vuldb.comvuldb.com/vuln/407460
vuldb.comvuldb.com/vuln/407460/cti

Frequently asked

questions

Yes, the description indicates that the affected functionality can be reached remotely. Exploitation still depends on network exposure and the specific route behavior in the deployed application.

It may not. The central risk is that a protected operation can be reached without successful authentication, although deployment-level controls could impose additional requirements.

Require authentication through a centralized, fail-closed dependency or middleware layer for every protected route, then perform explicit authorization checks based on server-validated identity and privileges.

Maintain an inventory of protected endpoints, require explicit security declarations in code review, test anonymous access in CI, and monitor production responses for unexpected successful unauthenticated requests.

Find out what's already
exploitable in your codebase.