WhatBrokeToday
GTA 6FAQ
Apache

Apache APISIX Authentication Bypass and Authorization Vulnerabilities

high

Is it fixed? Not yet.

Ongoing since Nov 13, 18:17 UTC. First reported Nov 13, 18:17 UTC.

What happened

Apache APISIX contains multiple high-severity vulnerabilities including an incorrect authorization flaw due to interpretation conflicts (CVE-2026-124680) affecting versions 0.9 through 3.19.0, and an authentication bypass by spoofing (CVE-2026-124679) affecting versions 3.18.0 through 3.19.0. Users are advised to upgrade to version 3.20.0.

What caused it?

Interpretation conflicts allow unauthenticated clients to reach upstream paths protected by route-level auth plugins under specific routing conditions, and authentication bypasses can occur via jwe-decrypt or forward-auth misconfigurations.

Workaround available

Upgrade to version 3.20.0

Reported inCVEevidence [2]
Official fix

Timeline

  1. Investigating(done)
  2. Workaround available(current)
  3. Resolved(upcoming)
  1. First report on security advisory

    Apache APISIX.: CVE-2026-124679 (High)

    Source
  2. Workaround discovered

    Workaround reported: Upgrade to version 3.20.0

    Source
  3. Status changed

    Status changed: new → workaround_available (workaround reported in source signals).

Evidence

2 reports · 2 CVEShow
  1. [1]
    CVE
    Apache APISIX.: CVE-2026-124679 (High)(opens security advisory in a new tab)

    High severity. Authentication bypass by spoofing vulnerability in Apache APISIX. On routes using jwe-decrypt with strict: false and a forward_header 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 allow_degradation: 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…

    by Tenable 0upvotes 0comments94% match

  2. [2]
    CVE First report
    Interpretation Conflict, resulting in (Incorrect Authorization) vulnerability in Apache APISIX.: CVE-2026-124680 (High)(opens security advisory in a new tab)

    High severity. Interpretation Conflict, resulting in (Incorrect Authorization) vulnerability in Apache APISIX. An unauthenticated client can reach upstream paths protected by a route-level auth plugin when a route without auth exists on the same upstream and the upstream does not collapse encoded dot segments. This issue affects Apache APISIX: from 0.9 through 3.19.0. Users are recommended to upgrade to version 3.20.0, which fixes the issue.

    by Tenable 0upvotes 0comments

FAQ

What happened in the Apache issue?

Apache APISIX contains multiple high-severity vulnerabilities including an incorrect authorization flaw due to interpretation conflicts (CVE-2026-124680) affecting versions 0.9 through 3.19.0, and an authentication bypass by spoofing (CVE-2026-124679) affecting versions 3.18.0 through 3.19.0. Users are advised to upgrade to version 3.20.0.

What is affected by the Apache issue?

Apache (versions: 0.9 through 3.19.0).

When did the Apache issue start and end?

It started Nov 13, 18:17 UTC and is still ongoing (5 d 10 h so far). This page updates as it develops.

How do I get alerts for Apache?

Subscribe to the Apache RSS feed for every new Apache incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Apache is down. Apache feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 2 reports from 1 independent source.