dbcve.org
ApisixApplication · Apache

CVE-2026-47339

HIGH · 8.1 CVSS v3.1 Published 2026-06-19
Fix available
A fix is available. Upgrade to 3.17.0 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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
Incorrect Authorization vulnerability in Apache APISIX. An attacker can capitalise on authz-casdoor plugin under default configuration to authenticate themselves with credentials from a different source. This issue affects Apache APISIX: from 2.14.1 through 3.16.0. Users are recommended to upgrade to version 3.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 · high confidence

The authz-casdoor plugin in Apache APISIX has an incorrect authorization vulnerability where the default configuration allows attackers to authenticate using credentials from an unintended source, effectively bypassing the intended access controls.

MitigationUpgrade Apache APISIX to version 3.17.0 or later and review the authz-casdoor plugin configuration to ensure credentials are validated against the correct identity provider.

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
Affected:>= 2.14.1, < 3.17.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Check Apache APISIX version
    Run the command `apisix version` or check the version via the control plane API at `/v1/version`
    Affected if The installed version is >= 2.14.1 and < 3.17.0
  2. Verify authz-casdoor plugin is loaded
    Check the enabled_plugins in apisix.yaml config file or query the APISIX Admin API endpoint `/v1/plugins` to list loaded plugins
    Affected if The authz-casdoor plugin appears in the list of enabled plugins
  3. Inspect authz-casdoor plugin configuration
    Query the APISIX Admin API at `/v1/plugin_configs` or `/v1/routes` to retrieve routes using the authz-casdoor plugin, or inspect the apisix.yaml configuration file for authz-casdoor settings
    Affected if The plugin is configured and the `endpoint` or `casdoor_server_url` parameter points to a Casdoor server that is not the intended identity provider, or if the default configuration is in use without explicit identity provider validation settings

You are affected if Apache APISIX version is between 2.14.1 and 3.16.x inclusive AND the authz-casdoor plugin is enabled with a configuration that does not explicitly validate credentials against the intended identity provider.

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 3.17.0 or later
Fixed in 3.17.0
Interim mitigation

Upgrade Apache APISIX to version 3.17.0 or later and review the authz-casdoor plugin configuration to ensure credentials are validated against the correct identity provider.

Recommended fix High confidence

3.17.0

  1. 1. Back up your current Apache APISIX configuration files (apisix.yaml, conf/config.yaml) and any custom plugins.
  2. 2. Review the Apache APISIX 3.17.0 release notes for any migration requirements or breaking changes specific to your configuration.
  3. 3. Stop the Apache APISIX service to prevent requests during upgrade.
  4. 4. Upgrade Apache APISIX to version 3.17.0 using your package manager or build process (e.g., 'yum upgrade apisix' or 'apt-get install apisix=3.17.0' depending on your OS).
  5. 5. Verify the upgrade was successful by checking the installed version (e.g., 'apisix version' or checking the startup logs).
  6. 6. Restore your configuration files from the backup if they were modified during package installation.
  7. 7. Start the Apache APISIX service.
  8. 8. Test the authz-casdoor plugin to confirm it functions correctly with the upgrade and that the authorization bypass vulnerability is fixed.
Caveat Review 3.17.0 release notes for any plugin or configuration changes; test in non-production first as with any major/minor upgrade

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

Fix this in Apisix Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47339 — 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-47339 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