ApisixApplication · Apache
CVE-2026-44915
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 · uneditedURL Redirection to Untrusted Site ('Open Redirect') vulnerability in Apache APISIX. The default configuration of cas-auth in Apache APISIX is vulnerable to phishing and credential theft. 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 · moderate confidenceThe cas-auth plugin in Apache APISIX contains an open redirect vulnerability in its default configuration, allowing attackers to craft malicious URLs that redirect users to phishing sites for credential theft.
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
>= 3.0.0, < 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache APISIX installation and versionRun `apisix version` or check the version in the startup logs to determine the installed Apache APISIX version.Affected if The installed version is 3.0.0 or higher but lower than 3.17.0
-
Locate the cas-auth plugin configuration fileSearch for the cas-auth plugin configuration in the APISIX config directory (typically under `conf/plugins/` or in `config.yaml` under the `plugins` section), or check if cas-auth is listed in the enabled plugins list.Affected if The cas-auth plugin is enabled in the APISIX configuration
-
Examine the cas-auth redirect URI configurationInspect the cas-auth plugin configuration file or the routes/upstreams that use the cas-auth plugin. Look for the `redirect_uri` or similar redirect-related configuration parameters.Affected if A redirect URI is configured and points to an untrusted or user-controlled domain, or the default configuration is in use without explicit safe redirect settings
-
Verify the redirect target allows external domainsReview the redirect URI configuration value. If it is set to a relative path or defaults to the APISIX host without strict domain validation, the vulnerability may be present.Affected if The redirect URI does not enforce strict domain validation or uses a default value that can be manipulated to an external domain
You are affected if Apache APISIX version is 3.0.0 or higher but below 3.17.0 AND the cas-auth plugin is enabled with a default or insecure redirect configuration.
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 3.17.0 or later to address the vulnerable default configuration in cas-auth.
3.17.0
- Backup your current Apache APISIX configuration files and any custom plugins
- Stop the running Apache APISIX service
- Upgrade Apache APISIX to version 3.17.0 using your chosen installation method (package manager, Docker, or source compilation)
- Verify the upgrade was successful by checking the installed version (e.g., apisix version command)
- Review the default cas-auth configuration in the new version to ensure the open redirect vulnerability is addressed
- Start the Apache APISIX service
- Test that the cas-auth functionality works correctly and that the open redirect is no longer present
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
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44915 — 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-44915 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