# CVE-2023-34047: Exposure of data and identity to wrong session in Spring for GraphQL

> Attackers can access sensitive session data and identity information from other sessions via batch loader functions in Spring for GraphQL.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Sep 2023
- **Updated:** 24 Sep 2024
- **Also known as:** GHSA-frqc-f2h8-fjvf

## What is CVE-2023-34047?

CVE-2023-34047 is a low-severity vulnerability in Spring for GraphQL, published on 20 Sep 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A batch loader function in Spring for GraphQL versions 1.1.0 - 1.1.5 and 1.2.0 - 1.2.2 may be exposed to GraphQL context with values, including security context values, from a different session. An application is vulnerable if it provides a DataLoaderOptions instance when registering batch loader functions through DefaultBatchLoaderRegistry.

## Which versions are affected by CVE-2023-34047?

4 open source packages ship an affected version, including org.springframework.graphql:spring-graphql. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.graphql:spring-graphql` | Maven | From 1.1.0 | 1.1.6 |
| `org.springframework.graphql:spring-graphql` | Maven | From 1.1.0 | 1.1.6 |
| `org.springframework.graphql:spring-graphql` | Maven | From 1.2.0 | 1.2.3 |
| `org.springframework.graphql:spring-graphql` | Maven | From 1.2.0 | 1.2.3 |

Products: Vmware Spring for Graphql.

## How do I fix CVE-2023-34047?

Upgrade org.springframework.graphql:spring-graphql to a fixed version for your release line: 1.1.6 or 1.2.3.

## Is CVE-2023-34047 being exploited?

There is no known exploitation of CVE-2023-34047 in the wild and no public exploit code.

## Other vulnerabilities in Spring for GraphQL

- [CVE-2026-59285](https://insights.sbomify.com/CVE-2026-59285/): Spring for GraphQL Unsafe Deserialization in pagination support (high 8.1)
- [CVE-2026-59286](https://insights.sbomify.com/CVE-2026-59286/): Spring for GraphQL loads Untrusted Resources in GraphiQL support (high 8.1)
- [CVE-2026-41699](https://insights.sbomify.com/CVE-2026-41699/): Unsafe Deserialization in Spring GraphQL (high 8.1)
- [CVE-2026-41700](https://insights.sbomify.com/CVE-2026-41700/): Cross-Site WebSocket Hijacking in Spring for GraphQL (high 8.1)
- [CVE-2026-59288](https://insights.sbomify.com/CVE-2026-59288/): Spring for GraphQL Information Exposure in GraphiQL support (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-34047 and fix it if it is affected.

What it is: CVE-2023-34047 is a low-severity vulnerability in Spring for GraphQL, published on 20 Sep 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-34047 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework.graphql:spring-graphql (Maven): affected from 1.1.0; fixed in 1.1.6
- org.springframework.graphql:spring-graphql (Maven): affected from 1.1.0; fixed in 1.1.6
- org.springframework.graphql:spring-graphql (Maven): affected from 1.2.0; fixed in 1.2.3
- org.springframework.graphql:spring-graphql (Maven): affected from 1.2.0; fixed in 1.2.3

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-34047/ (Markdown: https://insights.sbomify.com/CVE-2023-34047/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-34047
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-34047
- OSV: https://osv.dev/vulnerability/CVE-2023-34047

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-34047/
Summaries are generated and may contain mistakes; the official description above is the record.