How severe is CVE-2022-32532?

CVE-2022-32532 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-32532?

CVE-2022-32532 affects the following packages: org.apache.shiro:shiro-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-32532?

Update org.apache.shiro:shiro-core to 1.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-32532 is resolved across your whole dependency graph.

How do I detect CVE-2022-32532 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.shiro:shiro-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-32532 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2022-32532 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2022-32532, including 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-32532?

CVE-2022-32532 has an EPSS (Exploit Prediction Scoring System) score of 25.5%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2022-32532?

CVE-2022-32532 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-32532 published, and has it been updated?

CVE-2022-32532 was published on June 28, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2022-32532 — shiro-core

CRITICAL

CVE-2022-32532 is a critical-severity (CVSS 9.8) CWE-863 vulnerability in org.apache.shiro:shiro-core. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.shiro:shiro-core — see the affected versions and patch details below.

Authentication Bypass Vulnerability

Also known asGHSA-4cf5-xmhp-3xj7

Published

Jun 28, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

25.5%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.apache.shiro:shiro-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Apache Shiro before 1.9.1, A RegexRequestMatcher can be misconfigured to be bypassed on some servlet containers. Applications using RegExPatternMatcher with . in the regular expression are possibly vulnerable to an authorization bypass.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.shiro:shiro-core`	all versions	1.9.1`org.apache.shiro:shiro-core:1.9.1`

Affected Products

1 product · 1 configurations

Application

shiroapache

< 1.9.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Apache Shiro before 1.9.1, A RegexRequestMatcher can be misconfigured to…

github.comGithubJun 2022

Report on github.com

github.comGithubJun 2022

Report on github.com

github.comGithubJun 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.shiro:shiro-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.shiro:shiro-core to 1.9.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-32532 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Apache Shiro before 1.9.1, A RegexRequestMatcher can be misconfigured to be bypassed on some servlet containers. Applications using RegExPatternMatcher with `.` in the regular expression are possibly vulnerable to an authorization bypass.

O3 Security · Impact-Aware SCA

Is CVE-2022-32532 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-863CWE-863

Weaponization

No Nuclei template or Metasploit module yet. 4 public proof-of-concept references are listed on this page.

OpenSSF Scorecard

Package health score

shiro

8.6/10

Maintained10/10

Dependency-Update-Tool10/10

Code-Review8/10

Branch-Protection3/10

Vulnerabilities10/10

Assessed Nov 2, 2026

Timeline

First exploit

Jun 28, 2022

Same day as disclosure — rapid exploitation

Disclosed

Jun 28, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-32532

GHSA-4cf5-xmhp-3xj7

References

Advisorygithub.com · CVE 2022 32532.json Advisorynvd.nist.gov · CVE 2022 32532 Weblists.apache.org · y8260dw8vbm99oq7zv6y3mzn5ovk90xh Packagegithub.com · shiro

Related vulnerabilities

This CVE is critical severity; 3 of 8 other CVEs affecting shiro-core are rated as high or higher (top: critical).

CVE-2026-56130CVE-2026-49268CVE-2026-43827CVE-2026-23901CVE-2023-46749CVE-2022-40664CVE-2016-4437CVE-2021-41303

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-32532 — shiro-core

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-32532 in your dependencies?