Advisory record · GHSA-3h6f-g5f3-gc4w

Access Control Bypass in Spring Security

CVSS 9.1 CriticalCriticalEPSS 0.041 · 90th percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 19 Jul 2023, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.springframework.security:spring-security-configMaven>=5.6.0, <5.6.12 || >=5.7.0, <5.7.10 || >=5.8.0, <5.8.5 || >=6.0.0, <6.0.5 || >=6.1.0, <6.1.25.6.12, 5.7.10, 5.8.5, 6.0.5, 6.1.2
Identifiers
GHSA-3h6f-g5f3-gc4w · CVE-2023-34034
Weakness (CWE)
CWE-281 · CWE-284
Published
19 Jul 2023
Updated
28 Oct 2024

Machine-written summary

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

Spring Security's spring-security-config package, versions 5.6.0 to before 5.6.12, 5.7.0 to before 5.7.10, 5.8.0 to before 5.8.5, 6.0.0 to before 6.0.5, and 6.1.0 to before 6.1.2, is affected. The source describes a pattern-matching mismatch between Spring Security and Spring WebFlux when "**" is used as a pattern in WebFlux security configuration, which can lead to a security bypass; it gives few details on the exact conditions. Upgrade to 5.6.12, 5.7.10, 5.8.5, 6.0.5, 6.1.2 or later.

Written 8 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.1 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N CNA (vmware)
  • CISA KEV Not listed.
  • EPSS 0.041, the 90th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:13 UTC First seen by agentprime
  2. 31 Oct 2026, 15:13 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.