CVE-2026-124679: Apache APISIX: jwe-decrypt and forward-auth may pass a client-supplied identity header

Published Nov 13, 2026
·
Updated

Authentication bypass by spoofing vulnerability in Apache APISIX.

On routes using jwe-decrypt with strict: false and a forwardheader distinct from the token header an unauthenticated client can supply the value the upstream treats as gateway-decrypted plaintext. Similar can happen when forward-auth is configured with allowdegradation: true, and the auth service is unavailable.

This issue affects Apache APISIX: from 3.18.0 through 3.19.0.

Users are recommended to upgrade to version 3.20.0, which fixes the issue.

Affected Software

1 affected component
Apache APISIX>=3.18.0<=3.19.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade apache/apisix to a version that resolves this vulnerability.

    Fixed in 3.20.0

Event History

Nov 13, 2026
CVE Published
via MITRE·05:53 PM
Data Sourced
via MITRE·05:53 PM
DescriptionWeakness
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which APISIX deployments are exposed to this issue?

Affected versions are Apache APISIX 3.18.0 through 3.19.0. Exposure requires either a route using jwe-decrypt with strict set to false and a forward_header different from the token header, or forward-auth configured with allow_degradation set to true.

2

What must an attacker do to exploit the jwe-decrypt case?

An unauthenticated client can supply a value in the identity header that the upstream application treats as gateway-decrypted plaintext. This applies when the route's jwe-decrypt configuration uses strict: false and its forward_header differs from the token header.

3

When does the forward-auth configuration become vulnerable?

The forward-auth case can occur when allow_degradation is true and the authentication service is unavailable. Under those conditions, a client-supplied identity header may be passed through.

4

How should affected deployments be remediated?

Upgrade Apache APISIX to version 3.20.0, which fixes the issue. If an immediate upgrade is not possible, avoid the affected jwe-decrypt configuration and do not enable forward-auth degradation where an unavailable auth service could allow client-supplied identity headers through.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203