CVE-2026-44915: Apache APISIX open redirect in cas-auth plugin

CVE-2026-44915 · Severity: info · CVSS 2.1 · Published 2026-06-19

Apache APISIX, a popular cloud-native API gateway, contains a security flaw in its CAS authentication plugin. This vulnerability allows attackers to redirect users from a legitimate company URL to a malicious website. This technique is commonly used in phishing campaigns to trick employees into providing their login credentials on a fake site that looks official.

Technologies: Apache APISIX. Vendors: Apache.

Quick answers

Is CVE-2026-44915 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-44915 being exploited in the wild.
How severe is CVE-2026-44915?
Informational severity, with a CVSS score of 2.1, published 19 June 2026.
Which products and versions are affected?
Apache APISIX 3.0.0 through 3.16.0.
Is there a fix for CVE-2026-44915?
A patch was published on 2026-06-19: Fixed in version 3.17.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44915 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-44915?
Check whether you run Apache APISIX at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An Open Redirect vulnerability (CWE-601) exists in the default configuration of the cas-auth plugin in Apache APISIX. The flaw stems from the use of unsanitized cookie values during the authentication flow, allowing a remote attacker to craft a URL that redirects a victim to an arbitrary external domain. While the redirect itself does not grant direct access to the gateway, it is a primary vector for phishing attacks and credential harvesting. The issue is present in versions 3.0.0 through 3.16.0 and is resolved in version 3.17.0.

Affected products

  • Apache APISIX 3.0.0 through 3.16.0

Timeline

  • 2026-06-19: disclosed
  • 2026-06-19: advisory
  • 2026-06-19: patched: Fixed in version 3.17.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.