Skip to main content
VulnerabilityPublished

CVE-2026-45739: strawberry · Information Exposure

Affects strawberrySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.1 Low : upgrade to 0.315.4 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
3.1Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.315.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade strawberry and strawberry-graphql/strawberry to 0.315.4.

Affected software

ProductAffectedFixed in
strawberry-graphqlstrawberryAffected
  • >=0.288.4 <0.315.4
Fixed in
  • 0.315.4
PyPIstrawberry-graphql/strawberrypkg:pypi/strawberry-graphql/strawberryOther threatsAffected
  • >=0.288.4 <0.315.4
Fixed in
  • 0.315.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Strawberry GraphQL to version 0.315.4 or later, where this issue is patched. Until the upgrade is applied, avoid entering sensitive headers in the GraphiQL headers editor to prevent exposure via URL query strings. Patch status is confirmed by the vendor's versioning information indicating the fix in 0.315.4.

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.

References

Community reviews

Loading reviews…