Skip to main content
VulnerabilityPublished

CVE-2026-129347: DefaultPasswordService and SimpleCredentialsMatcher could treat an empty stored credential as a

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-129347· Low 2.3

Not known to be exploited · CVSS 2.3 Low : upgrade to 3.0.2 when convenient.

Data as of 16 Nov 2026, 17:21 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (apache)CVSS 4.02.3
Patch
Available – fixed in 3.0.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/S:N/AU:N/V:D/RE:L/U:Green

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade Apache Shiro and org.apache.shiro/shiro-core to 3.0.2.

Affected software

ProductAffectedFixed in
Apache Shiroorg.apache.shiro:shiro-coreAffected
  • <3.0.2
Fixed in
  • 3.0.2
Mavenorg.apache.shiro/shiro-corepkg:maven/org.apache.shiro/shiro-coreOther threatsAffected
  • <3.0.2
Fixed in
  • 3.0.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Apache Shiro to version 3.0.2 or later, which contains the official fix. Alternatively, ensure that no accounts have empty stored credentials and reject empty passwords in the application logic. These steps effectively mitigate the vulnerability.

Description

Apache Shiro versions through 3.0.1 have a vulnerability where DefaultPasswordService and SimpleCredentialsMatcher treat an empty stored credential as a valid match for an empty submitted password. This issue only arises if accounts with empty stored credentials exist. The vulnerability is fixed in version 3.0.2 and later. Mitigation includes upgrading to 3.0.2+ or avoiding empty stored credentials and rejecting empty passwords in the application.

References

Community reviews

Loading reviews…