# Apache Shiro LDAP Realm Authentication Bypass (CVE-2026-129349) and Apache APISIX Authentication Bypass (CVE-2026-124679)

> Two Apache authentication-bypass flaws were disclosed on 2026-11-13/14. Apache Shiro (shiro-core through 3.0.0) accepts any password for a previously logged-in user when DefaultLdapRealm/JndiLdapRealm runs with authenticationCachingEnabled=true (CVSS 4.0: 9.1). Apache APISIX 3.18.0-3.19.0 can be bypassed on jwe-decrypt routes with strict=false or forward-auth routes with allow_degradation=true while the auth service is down (CVSS 4.0: 7.8). Fixes: Shiro 3.0.1+, APISIX 3.20.0.

- **Published:** 2026-11-16T12:04:15Z
- **Last reviewed:** 2026-11-16T12:04:15Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-6140
- **Card image:** https://intel.threadlinqs.com/og/threat/TL-2026-6140.png
- **ID:** TL-2026-6140
- **Severity:** CRITICAL (CVSS 9.1)
- **Category:** VULNERABILITY
- **Status:** ACTIVE
- **Detections:** 9 (1 shown free below) · **IOCs:** 6
- **CVEs:** CVE-2026-129349, CVE-2026-124679

## Description

CVE-2026-129349 (Apache Shiro, CWE-287). When authentication caching is enabled on DefaultLdapRealm or JndiLdapRealm, the realm caches the authentication info after a successful login. Later logins for the same user are served from the cache and skip the LDAP bind. DefaultLdapRealm installs AllowAllCredentialsMatcher by default, which accepts any credentials, so an attacker who knows only a valid username of a user who has logged in once can authenticate with an arbitrary password. All shiro-core versions through 3.0.0 (before 3.0.1) are affected, but only when authenticationCachingEnabled is true; caching is not enabled by default. NVD records CVSS 4.0 9.1 (vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N) as a secondary metric supplied by the Apache Software Foundation. Credit: Joshua Rogers (finder), Lenny Primak (remediation developer, oss-security post 2026-11-14). Fix: Shiro 3.0.1 or later, which no longer installs AllowAllCredentialsMatcher by default. Workarounds: disable authentication caching on the LDAP realm, or configure a credentials matcher such as SimpleCredentialsMatcher that verifies submitted credentials against the cached authentication info.

CVE-2026-124679 (Apache APISIX, CWE-290 Authentication Bypass by Spoofing). Two configurations are affected. (1) Routes using the jwe-decrypt plugin with strict set to false and a forward_header that differs from the token header: an unauthenticated client can supply the value that the upstream treats as the gateway-decrypted plaintext. (2) Routes using forward-auth with allow_degradation set to true when the authentication service is unavailable, where requests are let through. Affected: APISIX 3.18.0 through 3.19.0. Fixed: 3.20.0. NVD records CVSS 4.0 7.8 (vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:H/SA:N), secondary metric from the Apache Software Foundation. Credit: Siyang Wu (reporter), shreemaan-abhishek (coordinator and remediation developer). The oss-security post lists no workarounds.

Scope notes: neither the GBHackers article nor the oss-security/NVD records state in-the-wild exploitation, a public PoC, or IOCs; none are asserted here. NVD status for both records is 'Received' (analysis pending) and neither is listed in CISA KEV in the sources reviewed. These CVEs are distinct from earlier 2026 Apache advisories with similar themes (Shiro CVE-2026-49268 LDAP DN injection; APISIX CVE-2026-49230 jwe-decrypt bypass, CVE-2026-39998 forward-auth header cleanup) and should not be conflated with them. The Shiro score uses the 4.0 AT:P attack-requirements metric, reflecting the non-default caching precondition. The IOCs listed are vulnerable-configuration and software indicators for exposure hunting, not attacker infrastructure; no network IOCs exist, so no BeaconBeagle correlation applies.

## MITRE ATT&CK

- T1190 Exploit Public-Facing Application
- T1078 Valid Accounts
- T1078 Valid Accounts
- T1556 Modify Authentication Process
- T1556 Modify Authentication Process
- T1212 Exploitation for Credential Access
- T1589.001 Credentials

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**Apache Shiro Username Enumeration and Arbitrary-Password Attempts Followed by Success (CVE-2026-129349 Precursor)** (`TL-2026-6140-SPL-002`)

CVE-2026-129349 needs only a valid username of a user who has logged in before, so attackers must guess or enumerate usernames (T1589.001, T1087.002) and submit arbitrary passwords (T1110.001 style attempts): failures for uncached or unknown users, then a success for a cached one with a wrong password. Detects one source trying 5 or more distinct usernames within 15 minutes with at least one failure and at least one success on the Shiro LDAP realms. Maps to T1589.001, T1087.002, T1110.001, T1078 and T1212.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1589.001, T1087.002, T1110.001, T1078, T1212
- **Data sources:** shiro:auth application log (index=app)
- **Severity:** high
- **Confidence:** medium

### Splunk SPL

```spl
index=app sourcetype="shiro:auth" realm IN ("DefaultLdapRealm","JndiLdapRealm") earliest=-30m
| bin _time span=15m
| stats dc(username) as distinct_users, count(eval(outcome=="failure")) as failures, count(eval(outcome=="success")) as successes, values(username) as users_tried by src_ip, _time
| where distinct_users>=5 AND failures>=1 AND successes>=1
| table _time src_ip distinct_users failures successes users_tried
```

### Microsoft KQL

```kql
ShiroAuth_CL
| where TimeGenerated > ago(30m)
| where realm_s in~ ("DefaultLdapRealm", "JndiLdapRealm")
| summarize distinct_users = dcount(tolower(username_s)),
            failures = countif(outcome_s =~ "failure"),
            successes = countif(outcome_s =~ "success"),
            users_tried = make_set(tolower(username_s), 25)
    by src_ip_s, bucket = bin(TimeGenerated, 15m)
| where distinct_users >= 5 and failures >= 1 and successes >= 1
```

### Sigma

```yaml
title: Apache Shiro LDAP Realm Login Events Base Rule for Username Enumeration
name: shiro_ldap_realm_login_events
id: 2e9b6d14-8a07-4c35-b1f2-6d3c9a1e5b02
status: experimental
description: Base rule matching all Shiro LDAP-realm login attempts. The correlation rule below fires when one source tries 5 or more distinct usernames in 15 minutes, the enumeration step that precedes the CVE-2026-129349 any-password login.
references:
    - http://www.openwall.com/lists/oss-security/2026/11/14/8
    - https://security.apache.org/projects/shiro/
author: Threadlinqs Team
date: 2026/11/16
tags:
    - attack.reconnaissance
    - attack.t1589.001
    - attack.discovery
    - attack.t1087.002
    - attack.credential-access
    - attack.t1110.001
    - attack.t1212
    - attack.initial-access
    - attack.t1078
    - cve.2026.129349
logsource:
    category: application
    product: apache_shiro
    service: authentication
detection:
    selection:
        realm:
            - 'DefaultLdapRealm'
            - 'JndiLdapRealm'
        outcome:
            - 'success'
            - 'failure'
    condition: selection
falsepositives:
    - Shared NAT or proxy egress addresses
level: informational
---
title: Apache Shiro Username Enumeration From Single Source (CVE-2026-129349 Precursor)
id: 5a8c3e70-1d94-4f26-8b0e-9c7d2f4a6b03
status: experimental
description: One source IP attempted 5 or more distinct usernames against Shiro LDAP realms within 15 minutes. Review for a following success, which is the CVE-2026-129349 any-password signature.
author: Threadlinqs Team
date: 2026/11/16
tags:
    - attack.reconnaissance
    - attack.t1589.001
    - attack.discovery
    - attack.t1087.002
    - attack.credential-access
    - attack.t1110.001
correlation:
    type: value_count
    rules:
        - shiro_ldap_realm_login_events
    group-by:
        - src_ip
    timespan: 15m
    condition:
        gte: 5
        field: username
falsepositives:
    - Shared NAT or proxy egress addresses
    - Load-test accounts
level: medium

```

**Known false positives:**

- Shared NAT or proxy egress IPs where many real users log in from one address
- Load-test or monitoring tools that cycle through test accounts

**Tuning notes:** Raise or lower distinct_users (5) and the 15m span for your traffic. Exclude known corporate egress ranges and monitoring hosts. Pivot on the successful username and run the SPL-001 bind-absence check for it. Because the bypass needs no password guessing, a success right after failures from the same source is the strongest signal; consider alerting on it alone for privileged usernames.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- APISIX jwe-decrypt Client-Supplied Forward Header Without Token Accepted (CVE-2026-124679) (locked: unlock with TL Creds)
- Shiro LDAP Realm Login From Previously Unseen Source for User (Cached-Auth Account Takeover) (locked: unlock with TL Creds)
- Vulnerable Apache Shiro shiro-core Version on Disk (CVE-2026-129349, through 3.0.0) (locked: unlock with TL Creds)
- APISIX Admin API Command Enabling allow_degradation or strict=false (CVE-2026-124679 Preconditions) (locked: unlock with TL Creds)
- Apache Shiro Realm Configuration File Modified (authenticationCachingEnabled / CVE-2026-129349) (locked: unlock with TL Creds)
- Vulnerable APISIX 3.18/3.19 Container Image Deployed (CVE-2026-124679) (locked: unlock with TL Creds)
- Apache Shiro LDAP Realm Login Success Without LDAP Bind (CVE-2026-129349 Cached-Auth Bypass) (locked: unlock with TL Creds)
- Apache APISIX forward-auth Outage With Requests Still Allowed (CVE-2026-124679 allow_degradation) (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sources

- [Apache Shiro and APISIX Security Flaws Let Attackers Bypass Authentication and Gain Unauthorized Access](https://gbhackers.com/apache-shiro-and-apisix-security-flaws/)
- [NVD API record for CVE-2026-129349 (Apache Shiro)](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-129349)
- [NVD API record for CVE-2026-124679 (Apache APISIX)](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-124679)
- [oss-security: CVE-2026-129349 Apache Shiro DefaultLdapRealm accepts any password with authentication caching](http://www.openwall.com/lists/oss-security/2026/11/14/8)
- [oss-security: CVE-2026-124679 Apache APISIX authentication bypass](http://www.openwall.com/lists/oss-security/2026/11/13/6)
- [Apache mailing list advisory - Shiro CVE-2026-129349 (cited by NVD; page content not retrievable)](https://lists.apache.org/thread/1whn52ht402lhc782c3s843c9hho8b4y)
- [Apache mailing list advisory - APISIX CVE-2026-124679 (cited by NVD; page content not retrievable)](https://lists.apache.org/thread/jmktj1o0rrxf1rdbptk0j3c4h0vdws96)
- [Apache Shiro security advisories](https://security.apache.org/projects/shiro/)
- [Apache APISIX security advisories](https://security.apache.org/projects/apisix/)
- [CVE.org record for CVE-2026-129349](https://www.cve.org/CVERecord?id=CVE-2026-129349)
- [CVE.org record for CVE-2026-124679](https://www.cve.org/CVERecord?id=CVE-2026-124679)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-6140
