Finding and attribution
Apache Shiro credential matching can incorrectly accept authentication in configurations containing accounts with empty stored credentials. The vendor documents a fix in version 3.0.2. The Apache disclosure credits an LLM security scan with finding the issue and the Shiro team with validation and reporting.
What to update · Apache Shiro
Affected versions not confirmed in this summary.
Remediation note: Apache documents version 3.0.2 or later as correcting the affected behavior; this is an upstream release statement, not verification of installed updates. The issue requires accounts with empty stored credentials; the vendor also recommends preventing that configuration.
Advisory / fix evidence · checked 21 Nov 2026
Product: Apache Shiro. AI system: ASF LLM-based security scan (specific model not disclosed). Team / organization: Apache Software Foundation; Apache Shiro.
CVE identifiers: CVE-2026-129347.
AI and human contribution (source account): The original dated Apache announcement and primary CNA credit attribute discovery to an ASF LLM security scan, with Apache Shiro validating and reporting the finding. The model is not named; no Claude-family attribution is transferred from a different Shiro case.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: Original Apache public announcement dated 14 November 2026 predates the CNA publication on 16 November. Unknown zero-day or exploitation status is not inferred.
Remediation status: fix documented.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 14 Nov 2026. AI attribution dated 14 Nov 2026. Sources checked 21 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Not available · no assessment established here. Documented technical effects: Not available.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
No source-backed CVSS assessment is established in this catalog.
Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.