# CVE-2026-45739: Strawberry GraphQL: Default GraphiQL may expose HTTP headers in URLs

> Strawberry GraphQL's default GraphiQL interface leaks sensitive HTTP headers into URLs, exposing them to logs and history.

- **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:** 4 Jun 2026
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-x97m-qp5c-w9xj, PYSEC-2026-2282

## What is CVE-2026-45739?

CVE-2026-45739 is a low-severity vulnerability in strawberry-graphql strawberry, published on 4 Jun 2026. 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

Strawberry GraphQL is a library for creating GraphQL APIs. In versions 0.288.4 through 0.315.3, Strawberry's bundled GraphiQL template wrote values from the GraphiQL headers editor into the browser URL query string. If a user entered a sensitive header, such as `Authorization: Bearer <token>`, the value could become visible in browser history, copied links, and server/proxy/CDN access logs after a page reload or shared request. Version 0.315.4 patches the issue.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-45739?

3 open source packages ship an affected version, including strawberry-graphql. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `strawberry-graphql` | PyPI | From 0.288.4 | 0.315.4 |
| `strawberry-graphql` | PyPI | From 0.288.4 | 0.315.4 |
| `strawberry-graphql` | PyPI | From 0.288.4 | 0.315.4 |

Products: Strawberry Strawberry Graphql.

## How do I fix CVE-2026-45739?

Upgrade strawberry-graphql to 0.315.4 or later.

## Is CVE-2026-45739 being exploited?

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

## Other vulnerabilities in strawberry-graphql strawberry

- [CVE-2026-35523](https://insights.sbomify.com/CVE-2026-35523/): Authentication bypass in strawberry-graphql via legacy graphql-ws WebSocket subprotocol (high 7.5)
- [CVE-2026-35526](https://insights.sbomify.com/CVE-2026-35526/): Strawberry GraphQL affected by a Denial of Service via unbounded WebSocket subscriptions (high 7.5)
- [CVE-2026-47706](https://insights.sbomify.com/CVE-2026-47706/): Strawberry GraphQL has a Circular Fragment Reference DOS (medium 5.3)
- [CVE-2026-47707](https://insights.sbomify.com/CVE-2026-47707/): Strawberry GraphQL's Bypass of MaxAliasesLimiter via Fragment Spreads leading to GraphQL Alias Amplification (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45739 and fix it if it is affected.

What it is: CVE-2026-45739 is a low-severity vulnerability in strawberry-graphql strawberry, published on 4 Jun 2026. 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-2026-45739 in the wild and no public exploit code.

Affected packages and fixed versions:
- strawberry-graphql (PyPI): affected from 0.288.4; fixed in 0.315.4
- strawberry-graphql (PyPI): affected from 0.288.4; fixed in 0.315.4
- strawberry-graphql (PyPI): affected from 0.288.4; fixed in 0.315.4

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

## Sources

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

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