dbcve.org
DragonflyApplication · Linuxfoundation

CVE-2026-24124

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-22
Fix available
A fix is available. Upgrade to 2.4.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Dragonfly is an open source P2P-based file distribution and image acceleration system. In versions 2.4.1-rc.0 and below, the Job API endpoints (/api/v1/jobs) lack JWT authentication middleware and RBAC authorization checks in the routing configuration. This allows any unauthenticated user with access to the Manager API to view, update and delete jobs. The issue is fixed in version 2.4.1-rc.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Dragonfly's Job API endpoints (/api/v1/jobs) are missing JWT authentication middleware and RBAC authorization checks in the routing configuration, allowing any unauthenticated user with network access to the Manager API to view, modify, and delete jobs.

MitigationUpgrade to Dragonfly version 2.4.1-rc.1 or later, and verify JWT authentication middleware and RBAC policies are correctly applied to all Job API endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DragonflyApplication
Affected:< 2.4.1= 2.4.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Dragonfly version
    Run 'dragonfly --version' or check the version in the service startup logs to determine the installed version.
    Affected if Version is less than 2.4.1 or equals 2.4.1
  2. Verify Job API endpoint accessibility
    Send an unauthenticated HTTP GET request to /api/v1/jobs (e.g., curl -s http://<manager-host>:<port>/api/v1/jobs) and observe the response.
    Affected if The endpoint returns job data or a 200/401 response instead of requiring authentication (e.g., 401 with auth prompt)
  3. Inspect JWT authentication middleware configuration
    Examine the Dragonfly configuration file (commonly dragonfly.yaml or dragonfly.conf) for auth.jwt or middleware.jwt settings, and verify they apply to /api/v1/jobs routes.
    Affected if No JWT middleware is defined, or the /api/v1/jobs paths are excluded from JWT protection
  4. Check RBAC policy for Job API
    Review RBAC or role-based access control configuration files to confirm if authorization policies are defined for the jobs API endpoints.
    Affected if No RBAC policies exist for /api/v1/jobs, or policies do not enforce authentication requirements
  5. Test job modification without credentials
    Send an unauthenticated HTTP POST or DELETE request to /api/v1/jobs/<job-id> (e.g., curl -X DELETE http://<manager-host>:<port>/api/v1/jobs/<any-id>)
    Affected if The request succeeds or returns a 200/204 status instead of being rejected due to missing authentication

If the installed Dragonfly version is 2.4.1 or earlier and the Job API responds to unauthenticated requests without JWT or RBAC enforcement, the environment is affected.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.1 or later
Fixed in 2.4.1
Vendor patch github.com →
Interim mitigation

Upgrade to Dragonfly version 2.4.1-rc.1 or later, and verify JWT authentication middleware and RBAC policies are correctly applied to all Job API endpoints.

Recommended fix High confidence

2.4.1-rc.1

  1. Upgrade Dragonfly to version 2.4.1-rc.1 or later to include the JWT authentication middleware and RBAC authorization fixes for the Job API endpoints (/api/v1/jobs)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dragonfly Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24124 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24124 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data