Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-p836-389h-j692

Improper Access Control in Apache Shiro

CVSS 9.8 CriticalCriticalIn CISA KEVEPSS 0.93 · 99th percentile

Critical, because:

  • In CISA’s KEV catalogue since 3 Nov 2021: it is known to be exploited.
  • CVSS score 9.8: 9.0 or more.
  • CVSS score 9.8 (7.0 or more) and EPSS 0.93 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 14 May 2022, 02:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.shiro:shiro-coreMaven<1.2.51.2.5
Identifiers
GHSA-p836-389h-j692 · CVE-2016-4437
Weakness (CWE)
CWE-284 · CWE-321
Tags
Published
14 May 2022
Updated
22 Oct 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Shiro (shiro-core) versions before 1.2.5 are affected when no cipher key is configured for the "remember me" feature. A remote attacker can exploit this through an unspecified request parameter to execute arbitrary code or bypass access restrictions. Upgrade shiro-core to 1.2.5 or later. The source gives few details on the exact parameter involved.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:H GitHub Advisory Database
  • CISA KEV Listed since 3 Nov 2021: known to be exploited.
  • EPSS 0.93, the 99th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:10 UTC First seen by agentprime
  2. 31 Oct 2026, 15:10 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.