Two Apache initiatives have disclosed authentication bypass vulnerabilities. One is a vital flaw in Apache Shiro’s LDAP realm.
The opposite is a high-severity identification spoofing difficulty within the Apache APISIX API gateway. Each flaws let an attacker acquire entry with out legitimate credentials and rely upon particular configurations.
Apache Shiro and APISIX Safety Flaws
The Shiro flaw is tracked as CVE-2026-129349 and carries a CVSS 4.0 rating of 9.1 (vital). It impacts all Apache Shiro variations by means of 3.0.0 (shiro-core), however solely when DefaultLdapRealm or JndiLdapRealm runs with authenticationCachingEnabled set to true.
That setting shouldn’t be the default. As soon as a person logs in efficiently, the realm caches the authentication. Later logins for that person skip the LDAP bind. The AllowAllCredentialsMatcher, which DefaultLdapRealm installs by default, then accepts any password. An attacker who is aware of solely a sound username can authenticate as that person. Joshua Rogers discovered the flaw, and Lenny Primak developed the repair.
Maintainers advocate upgrading to Shiro 3.0.1 or later, which not installs AllowAllCredentialsMatcher by default. Directors who can not improve can flip off authentication caching on the LDAP realm.
They’ll additionally configure a stricter credentials matcher, equivalent to SimpleCredentialsMatcher, which checks credentials towards the cached authentication information. Groups ought to assessment their realm settings, as a result of the Apache Shiro undertaking paperwork these choices.
The APISIX flaw, CVE-2026-124679, scores 7.8 (excessive) underneath CVSS 4.0. It impacts Apache APISIX 3.18.0 by means of 3.19.0. The problem is an authentication bypass by spoofing.
On routes that use the jwe-decrypt plugin with strict set to false and a forward_header completely different from the token header, an unauthenticated consumer can provide the header worth. The upstream service then treats that worth as plaintext that the gateway has decrypted.
An analogous situation arises when forward-auth runs with allow_degradation set to true and the authentication service is unavailable. Siyang Wu reported the problem, and the undertaking fastened it in model 3.20.0.
The flaw reveals how dangerous it’s to belief identification headers that purchasers can set. Gateways are supposed to be the one enforcement level so {that a} spoofed header can hand attackers the identification of a official person.
APISIX has had identity-handling issues earlier than. An earlier Apache APISIX difficulty involving cross-issuer entry additionally let attackers cross identification boundaries underneath particular misconfigurations. Comparable belief failures have hit different gateways. For instance, uncovered Clawdbot gateways auto-approved site visitors that got here by means of a reverse proxy.
Affect relies on how a company has configured its methods. Environments that mix permissive plugin settings with an upstream that blindly trusts headers face the very best publicity.
The identical applies to Shiro deployments that turned on LDAP authentication caching for efficiency. In actual incidents, authentication bypasses like these have typically been step one towards wider compromise.
Give your SOC the alert context on the newest threats to cease incidents rapidly -> Combine Risk Intel from 16K SOCs:







