ApisixApplication · Apache
CVE-2026-39999
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 · uneditedAuthentication Bypass by Spoofing vulnerability in Apache APISIX. The attacker can completely bypass authentication capitalising on certain configurations of jwt-auth plugin. This issue affects Apache APISIX: from v2.2 through v3.16.0. Users are recommended to upgrade to version v3.17.0, which fixes the issue.
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 · moderate confidenceAuthentication bypass vulnerability in Apache APISIX's jwt-auth plugin allows attackers to completely bypass authentication by spoofing JWT tokens in certain plugin configurations. The spoofing attack vector enables unauthorized access to protected APIs without valid credentials.
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
ApisixApplication
>= 2.2, < 3.17.0CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache APISIX versionRun 'apisix version' or check the version file in the APISIX installation directoryAffected if Installed version is >= 2.2 and < 3.17.0
-
Verify jwt-auth plugin is enabledCheck the APISIX config.yaml file or query the /v1/plugins endpoint for plugin statusAffected if The jwt-auth plugin is loaded and active in the configuration
-
Inspect jwt-auth plugin configurationReview the jwt-auth configuration in config.yaml or in route/consumer definitions for token spoofing vulnerabilities (e.g., insecure token verification settings)Affected if The plugin configuration contains settings that allow token spoofing or weak validation
-
Audit routes using jwt-authQuery APISIX routes via /v1/routes or review route configurations to identify which routes use the jwt-auth pluginAffected if Any routes are configured to use jwt-auth for authentication protection
The environment is affected if APISIX version is between 2.2 and 3.16.x inclusive and the jwt-auth plugin is enabled with a vulnerable configuration that permits JWT token spoofing.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.17.0
Upgrade Apache APISIX to version v3.17.0 or later. If immediate upgrading is not feasible, audit and restrict jwt-auth plugin configurations to eliminate token spoofing vectors.
3.17.0
- 1. Backup your current Apache APISIX configuration and data directories
- 2. Download Apache APISIX version 3.17.0 from the official Apache repository (https://apisix.apache.org/downloads/)
- 3. Upgrade APISIX to version 3.17.0 using your package manager or by following the official upgrade guide at https://apisix.apache.org/docs/apisix/next/upgrade-guide/
- 4. Restart the APISIX service to load the new version
- 5. Verify that the jwt-auth plugin is functioning correctly with the new version
- 6. Test that authentication is properly enforced and the bypass vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Apisix
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39999 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-39999 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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