NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
CRITICAL severity

Access Control Bypass in Spring SecurityGHSA-3h6f-g5f3-gc4w

CRITICAL

GHSA-3h6f-g5f3-gc4w is a critical-severity (CVSS 9.1) CWE-281 vulnerability in org.springframework.security:spring-security-config. A fix is available for org.springframework.security:spring-security-config — see the affected versions and patch details below.

Also known asCVE-2023-34034
Published
Updated
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-3h6f-g5f3-gc4w.

EPSS Exploitation Probability

via FIRST.org ↗
4.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk
0.00%21.0%42.0%63.0%47.9%4.1%May 26Sep 26Nov 26

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

5 pkgs affected
☕org.springframework.security:spring-security-config☕org.springframework.security:spring-security-config☕org.springframework.security:spring-security-config☕org.springframework.security:spring-security-config☕org.springframework.security:spring-security-config

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

Using "**" as a pattern in Spring Security configuration for WebFlux creates a mismatch in pattern matching between Spring Security and Spring WebFlux, and the potential for a security bypass.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.springframework.security:spring-security-config≥ 5.6.0&&< 5.6.125.6.12org.springframework.security:spring-security-config:5.6.12
☕Mavenorg.springframework.security:spring-security-config≥ 5.7.0&&< 5.7.105.7.10org.springframework.security:spring-security-config:5.7.10
☕Mavenorg.springframework.security:spring-security-config≥ 5.8.0&&< 5.8.55.8.5org.springframework.security:spring-security-config:5.8.5
☕Mavenorg.springframework.security:spring-security-config≥ 6.0.0&&< 6.0.56.0.5org.springframework.security:spring-security-config:6.0.5
☕Mavenorg.springframework.security:spring-security-config≥ 6.1.0&&< 6.1.26.1.2org.springframework.security:spring-security-config:6.1.2

Affected Products

1 product · 5 configurations
Application
spring securityvmware
≥ 6.1.0 && < 6.1.2
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update org.springframework.security:spring-security-config to 5.6.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3h6f-g5f3-gc4w is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant
Workaround published by Red Hat
Users of path-based URL determination should ensure that all their patterns have a slash prepended. example: pathMatchers("home/**") // vulnerable pathMatchers("/home/**") // not vulnerable
Source: Red Hat security advisory for GHSA-3h6f-g5f3-gc4w (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Fuse 7.12.1spring-securityRHSA-2023:7247

Frequently Asked Questions

Using "**" as a pattern in Spring Security configuration for WebFlux creates a mismatch in pattern matching between Spring Security and Spring WebFlux, and the potential for a security bypass.
O3 Security · Impact-Aware SCA

Is GHSA-3h6f-g5f3-gc4w in your dependencies?

Find it across Maven, including transitive dependencies.

Access Control Bypass in Spring Security (Critical 9.1)