dbcve.org
ApisixApplication · Apache

CVE-2026-49872

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
Improper Authentication vulnerability in Apache APISIX. When the cas-auth plugin is used in a route, an attacker can possibly authenticate itself with credentials from a different source. This issue affects Apache APISIX: from 3.0.0 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 cas-auth plugin in Apache APISIX versions 3.0.0-3.16.0 contains an improper authentication vulnerability that allows attackers to authenticate using credentials from a different source than intended, potentially bypassing proper authentication controls.

MitigationUpgrade Apache APISIX to version 3.17.0 or later to obtain the security fix for this improper authentication vulnerability.

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:>= 3.0.0, < 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. Determine Apache APISIX installed version
    Run 'apisix version' or check the package manager (e.g., 'apt list --installed | grep apisix' or 'rpm -qa | grep apisix') to find the installed APISIX version number
    Affected if The installed version is 3.0.0 through 3.16.0 (any version >= 3.0.0 and < 3.17.0)
  2. Verify cas-auth plugin is enabled
    Check the APISIX configuration file (conf/config.yaml) under the 'plugins' or 'enable_plugins' section, or query the admin API endpoint /apisix/admin/plugins/list to list enabled plugins
    Affected if The cas-auth plugin appears in the enabled plugins list
  3. Check cas-auth plugin configuration
    Query the APISIX admin API at /apisix/admin/plugin_configs or inspect the route/consumer configuration where cas-auth is applied (look for 'cas_auth' or 'cas-auth' in plugin configuration)
    Affected if The cas-auth plugin is actively configured for authentication on any route or consumer

User is affected if running Apache APISIX version 3.0.0-3.16.0 AND the cas-auth plugin is enabled and configured for authentication

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 to obtain the security fix for this improper authentication vulnerability.

Recommended fix High confidence

3.17.0

  1. Review the Apache APISIX 3.17.0 release notes and changelog to understand changes and any migration requirements
  2. Create a backup of your current APISIX configuration, including route definitions, plugin configurations, and etcd data
  3. Test the upgrade in a staging environment before applying to production
  4. Stop the Apache APISIX services
  5. 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/next
  6. Verify that the cas-auth plugin is functioning correctly after upgrade
  7. Test that authentication works properly with the expected credential source
  8. Monitor logs for any authentication-related errors
Caveat Review the changelog between your current version and 3.17.0; major/minor upgrades may introduce breaking changes in plugin behavior or configuration syntax

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

Fix this in Apisix Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing8.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,080
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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