CVE-2023-27584 is a critical authentication bypass in Dragonfly, the CNCF P2P file distribution and image acceleration system. Its JWT secret key is hard coded, so an attacker can act as an admin. NVD and the project score it 9.8. Upgrade to v2.0.9 or later.
What's affected
- Dragonfly (Go module github.com/dragonflyoss/Dragonfly2): the GitHub advisory lists version 2.0.8 as affected.
- Fixed: v2.0.9. The advisory says to use Dragonfly v2.0.9 and above.
The NVD description says the issue was addressed in release 2.0.9 and does not give a start version. Where the two differ, the sensible reading is that releases before 2.0.9 should be treated as affected, and confirm the range for your version in the advisory.
Severity agrees across sources: 9.8, Critical, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
How to check if you're exposed
Check which Dragonfly version your cluster runs. For Go projects that import the module, list it with:
go list -m all | grep Dragonfly2
For deployed manager and scheduler components, read the version from your deployment manifest, Helm values or container image tag. Anything below v2.0.9 needs the upgrade.
Also check whether the Dragonfly manager API is reachable from outside your cluster. If it is, the exposure is higher.
What to do now
- Upgrade Dragonfly to v2.0.9 or later in every environment.
- After upgrading, review the manager's user list and recent admin actions for anything unexpected, because a forged token leaves no password trail.
- Restrict network access to the manager so that only trusted clients can reach it.
- The advisory lists one stopgap: temporarily disabling JWT authentication if it is not critical for your deployment. Treat it as a short-term measure only, and note that the project says there are no known workarounds.
- Scan your dependency list for the Dragonfly2 module to find other projects that import it.
Why it matters
The record classes the flaw as CWE-321 (Use of Hard-coded Cryptographic Key) and CWE-798 (Use of Hard-coded Credentials). A JWT is only trustworthy if the key that signs it is secret. When the key is the same in every installation and sits in the source code, anyone who reads the code can sign a token that the server accepts.
That turns authentication into a formality, which is why the vector needs no privileges and no user interaction. The CISA Known Exploited Vulnerabilities flag is false for this record, and I found no report of exploitation in the sources I read. The lesson holds anyway: secrets that ship in code are public, so rotate or generate them per installation.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Is there a workaround?
The GitHub advisory suggests disabling JWT authentication temporarily where it is not critical, but the NVD text says there are no known workarounds. Upgrade to v2.0.9 or later.
Sources
Last reviewed: 19 October 2026.