A week after 38 advisories, Camel published seven more on 22 October, led by a High-rated XXE in camel-saxon. On the 4.22 LTS line only 4.22.2 fixes them; 4.18.5 and 4.23.0 already do.
Apache Shiro flaw let cached LDAP logins accept any password
EditorialBy TrustList Editorial
CVE-2026-129349 is critical where DefaultLdapRealm runs with authentication caching on; 3.0.1 fixes it with several other flaws, and 3.0.2 fixes four low-severity issues found since.
- Java
- Authentication
- Cybersecurity
- Web Security
About Apache Shiro flaw let cached LDAP logins accept any password
Apache Shiro flaw let cached LDAP logins accept any password
16 November 2026: Apache Shiro, the Java security framework, has fixed CVE-2026-129349, a critical flaw that lets an attacker who knows a valid username log in as that user with any password, once the real user has signed in successfully. It affects every version up to 3.0.0, but only applications that use DefaultLdapRealm or JndiLdapRealm with authenticationCachingEnabled set to true, which is not the default. Version 3.0.1 fixes it.
Not yet independently verified. The Apache Shiro security page gives no publication date for these entries; the date is that of Belgium's Centre for Cybersecurity warning, which scores CVE-2026-129349 at 9.1 on CVSS 4.0. We will update this when it can be confirmed, and remove this note.
Why the cache skipped the password check
The realm checks a password by binding to the LDAP directory. Once a login is cached, that bind is skipped, and the credentials matcher DefaultLdapRealm installed by default, AllowAllCredentialsMatcher, accepted whatever was offered. Shiro 3.0.1 no longer installs that matcher by default.
Where an upgrade has to wait, the project gives two workarounds: turn authentication caching off on the LDAP realm, which is the default setting, or set a credentials matcher such as SimpleCredentialsMatcher that checks the password against the cached information. Belgium's Centre for Cybersecurity scores the flaw 9.1 on CVSS 4.0 and told Shiro users on 16 November to patch with the highest priority. Joshua Rogers reported it.
More fixes in 3.0.1, four in 3.0.2
The project's security page lists the other flaws fixed by 3.0.1, among them:
- CVE-2026-74762, medium: session fixation when a user is restored from a "Remember me" cookie, and session IDs accepted from the URL even with URL rewriting off;
- CVE-2026-58301 and CVE-2026-88019, both in the Jakarta EE integration module: a request that makes the server connect to an attacker's URL, and form resubmission after login that can drop cookie security attributes and send data to an untrusted host.
A later release, 3.0.2, fixes four low-severity issues in 3.0.1 and earlier: an incomplete case-sensitivity fix in a manually created ShiroFilterFactoryBean (CVE-2026-114737), empty stored passwords matching an empty submitted one (CVE-2026-129347), unescaped output in the shiro:principal tags (CVE-2026-129320), and removed users that stay active after PropertiesRealm reloads its file (CVE-2026-129348).
Finding Shiro in your estate
Shiro is often a transitive dependency, pulled in by an application framework or a vendor product rather than chosen directly, so a dependency scan is the quickest way to see where it runs. Only the newest release line gets every security fix, the project says; older lines need commercial support.
The LDAP flaw matters most for internal portals and admin consoles that sign staff in against Active Directory or another LDAP directory.
Sources
- Apache Shiro: Vulnerability reports, 18 November 2026
- Centre for Cybersecurity Belgium: Improper authentication vulnerability in Apache Shiro, patch immediately, 16 November 2026
Categories & features
- Java
- Authentication
- Cybersecurity
- Web Security
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
CVE-2026-114938 hits OpenJDK 17.0.6 and later on x86-64 servers with AVX-512 VBMI; the 17 November updates fix it, and two JVM flags switch the faulty code off.
Oracle scores the Java gap 9.1 and pulls the eMudhra roots from every supported JDK line; Cisco lists Duo upgrades now, Meraki camera firmware on 18 November and IOS XR 26.4.1 on 30 November.
Two flaws rated Important hit all three supported lines, a third affects only Tomcat 11, and the fixed releases have been out since 12 October.
CERT Polska coordinated CVE-2026-59074 to CVE-2026-59081 in the Polish CMS: version 5.10.2607 fixes seven, 5.8 gets hotfixes, and tokens sent in query strings stay unfixed.
CVE-2026-114509 lets an attacker with no token log in as an existing user on apps using TokenGuard with MySQL or MariaDB. Upgrade to 13.29.0 or 12.68.0; a proof of concept is public.
The quarterly advisory covers Java 8 to 27, with a top score of 7.0, and a separate notice adds the 9.1-rated TLS flaw CVE-2026-91403. Amazon Corretto shipped 27.0.1, 25.0.5, 21.0.13, 17.0.21, 11.0.33 and 8u512.
CVE-2026-91403 in JSSE can be exploited over the network with no login. Every listed build is affected, including 25.0.5 and 21.0.13, so Java estates need to patch again.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More JavaThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.