dbcve.org
ApisixApplication · Apache

CVE-2026-48895

HIGH · 7.2 CVSS v3.1 Published 2026-06-19
Fix available
A fix is available. Upgrade to 3.17.0 or later.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges 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
URL Redirection to Untrusted Site ('Open Redirect') vulnerability in Apache APISIX. The attacker could manipulate some client headers to perform an open-redirect, to potentially expose the session token. 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

Open redirect vulnerability in Apache APISIX allows attackers to manipulate client headers to redirect users to untrusted sites, potentially exposing session tokens. Affects versions 3.0.0 through 3.16.0.

MitigationUpgrade to Apache APISIX version 3.17.0 or later which contains the fix for this 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
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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 installed Apache APISIX version
    Run 'apisix version' command or check Docker image version with 'docker images | grep apisix'
    Affected if Version is 3.0.0 through 3.16.0 (or any version below 3.17.0)
  2. Verify proxy-redirect module configuration
    Examine APISIX configuration file (config.yaml) for 'proxy_redirect' directive settings
    Affected if proxy_redirect is enabled and configured to use client-supplied header values
  3. Check upstream redirect handling
    Review route and upstream configurations for 'proxy_redirect' or 'location' header manipulation settings
    Affected if Upstream responses can modify redirect locations based on client headers
  4. Identify exposed admin or proxy endpoints
    Review APISIX listening ports and check if admin API or proxy ports are accessible from untrusted networks
    Affected if Admin API is accessible without proper authentication or proxy port accepts arbitrary header manipulation

If APISIX version is 3.0.0 through 3.16.0 and proxy-redirect or upstream redirect configurations allow client-controlled header values, the environment is vulnerable to open redirect attacks.

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 to Apache APISIX version 3.17.0 or later which contains the fix for this vulnerability.

Recommended fix High confidence

3.17.0

  1. Review the current Apache APISIX installation and confirm the exact version running (e.g., check the version endpoint or packaging metadata)
  2. Create a backup of the current Apache APISIX configuration files, including apisix.yaml, config.yaml, and any related YAML files in the conf.d directory
  3. Stop the Apache APISIX service to prevent any requests during the upgrade process
  4. Upgrade Apache APISIX to version 3.17.0 using the appropriate package manager or installation method (e.g., yum, apt, Docker image, or source compilation)
  5. After upgrading, verify that the new version 3.17.0 is correctly installed by checking the version
  6. Review the Apache APISIX configuration files to ensure compatibility with version 3.17.0, as default configurations may have changed
  7. Start the Apache APISIX service and verify that it starts without errors
  8. Test the application functionality, particularly any routes that involve client header manipulation, to confirm the open redirect vulnerability is resolved
Caveat Review Apache APISIX 3.17.0 release notes for any configuration changes or deprecations that may affect existing routes or plugins

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

Fix this in Apisix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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