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

Low 3.1 Published Updated

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

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

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, CWE-200

Which versions are affected by CVE-2026-45739?

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

PackageAffectedFixed in
strawberry-graphql PyPIFrom 0.288.40.315.4
strawberry-graphql PyPIFrom 0.288.40.315.4
strawberry-graphql PyPIFrom 0.288.40.315.4

Products include 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.

Sources

Also known as GHSA-x97m-qp5c-w9xj, PYSEC-2026-2282.

Is CVE-2026-45739 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free