# CVE-2023-34034: Access Control Bypass in Spring Security > Attackers can bypass security controls in Spring WebFlux applications by exploiting pattern matching mismatches in Spring Security configurations. - **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 Jul 2023 - **Updated:** 1 May 2026 - **Also known as:** GHSA-3h6f-g5f3-gc4w ## What is CVE-2023-34034? CVE-2023-34034 is a critical vulnerability in Spring Security, published on 19 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-281 (Improper Preservation of Permissions) ## Which versions are affected by CVE-2023-34034? 10 open source packages ship an affected version, including org.springframework.security:spring-security-config. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework.security:spring-security-config` | Maven | From 5.6.0 | 5.6.12 | | `org.springframework.security:spring-security-config` | Maven | From 5.6.0 | 5.6.12 | | `org.springframework.security:spring-security-config` | Maven | From 5.7.0 | 5.7.10 | | `org.springframework.security:spring-security-config` | Maven | From 5.7.0 | 5.7.10 | | `org.springframework.security:spring-security-config` | Maven | From 5.8.0 | 5.8.5 | | `org.springframework.security:spring-security-config` | Maven | From 5.8.0 | 5.8.5 | | `org.springframework.security:spring-security-config` | Maven | From 6.0.0 | 6.0.5 | | `org.springframework.security:spring-security-config` | Maven | From 6.0.0 | 6.0.5 | | `org.springframework.security:spring-security-config` | Maven | From 6.1.0 | 6.1.2 | | `org.springframework.security:spring-security-config` | Maven | From 6.1.0 | 6.1.2 | Products: Vmware Spring Security. ## How do I fix CVE-2023-34034? Upgrade org.springframework.security:spring-security-config to a fixed version for your release line: 5.6.12, 5.7.10, 5.8.5 or 6.0.5. ## Is CVE-2023-34034 being exploited? There is no known exploitation of CVE-2023-34034 in the wild and no public exploit code. Public exploit code: - Demonstration of CVE-2023-24034 authorization bypass in Spring Security (github_poc): https://github.com/hotblac/cve-2023-34034 ## Other vulnerabilities in Spring Security - [CVE-2014-3527](https://insights.sbomify.com/CVE-2014-3527/): Authorization Bypass in Spring Security (critical 9.8) - [CVE-2026-59354](https://insights.sbomify.com/CVE-2026-59354/): Spring Security OAuth2 Authorization Server: Insufficient validation of Dynamic Client Registration metadata (critical 9.6) - [CVE-2026-59270](https://insights.sbomify.com/CVE-2026-59270/): Spring Security embedded UnboundID LDAP server exposes well-known administrative bind DN on all network interfaces (critical 9.4) - [CVE-2026-22732](https://insights.sbomify.com/CVE-2026-22732/): Under Some Conditions Spring Security HTTP Headers Are not Written (critical 9.1) - [CVE-2026-47877](https://insights.sbomify.com/CVE-2026-47877/): Spring Security Authorization Server Default Consent Page is vulnerable to Cross-Site Scripting (XSS) (high 8.2) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-34034 and fix it if it is affected. What it is: CVE-2023-34034 is a critical vulnerability in Spring Security, published on 19 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-34034 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework.security:spring-security-config (Maven): affected from 5.6.0; fixed in 5.6.12 - org.springframework.security:spring-security-config (Maven): affected from 5.6.0; fixed in 5.6.12 - org.springframework.security:spring-security-config (Maven): affected from 5.7.0; fixed in 5.7.10 - org.springframework.security:spring-security-config (Maven): affected from 5.7.0; fixed in 5.7.10 - org.springframework.security:spring-security-config (Maven): affected from 5.8.0; fixed in 5.8.5 - org.springframework.security:spring-security-config (Maven): affected from 5.8.0; fixed in 5.8.5 - org.springframework.security:spring-security-config (Maven): affected from 6.0.0; fixed in 6.0.5 - org.springframework.security:spring-security-config (Maven): affected from 6.0.0; fixed in 6.0.5 - org.springframework.security:spring-security-config (Maven): affected from 6.1.0; fixed in 6.1.2 - org.springframework.security:spring-security-config (Maven): affected from 6.1.0; fixed in 6.1.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-34034/ (Markdown: https://insights.sbomify.com/CVE-2023-34034/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-34034 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-34034 - OSV: https://osv.dev/vulnerability/CVE-2023-34034 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-34034/ Summaries are generated and may contain mistakes; the official description above is the record.