CVE-2026-45739

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. Limited direct impact.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-06-04 15:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-07-22 20:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 3.1 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-06-04 15:16 UTC

Last modified

2026-07-22 20:10 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-200 · Information exposure

Record status

Analyzed

Affected

• Strawberry Graphql < 0.315.4

Attack profile CVSS 3.1 · 3.1

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-45739.md and follow it. Check whether this project is affected by CVE-2026-45739. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge