CVE-2026-45739: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in strawberry-graphql strawberry
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.
AI Analysis
Technical Summary
Strawberry GraphQL's bundled GraphiQL template in versions 0.288.4 to 0.315.3 improperly writes header values from the GraphiQL headers editor into the browser URL query string. This behavior can expose sensitive information like 'Authorization: Bearer <token>' in browser history, copied links, and server/proxy/CDN logs after page reloads or when sharing requests. The vulnerability is classified under CWE-200 (Exposure of Sensitive Information) and CWE-201 (Information Exposure Through Sent Data). Version 0.315.4 includes a patch that resolves this issue.
Potential Impact
Sensitive information such as authorization tokens can be exposed to unauthorized actors through browser history, shared URLs, and server or proxy logs. This exposure could potentially lead to information disclosure but does not directly impact integrity or availability. The CVSS score of 3.1 reflects a low impact severity.
Mitigation Recommendations
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.
CVE-2026-45739: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in strawberry-graphql strawberry
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.
CVSS v3.1
Score 3.1low
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Strawberry GraphQL's bundled GraphiQL template in versions 0.288.4 to 0.315.3 improperly writes header values from the GraphiQL headers editor into the browser URL query string. This behavior can expose sensitive information like 'Authorization: Bearer <token>' in browser history, copied links, and server/proxy/CDN logs after page reloads or when sharing requests. The vulnerability is classified under CWE-200 (Exposure of Sensitive Information) and CWE-201 (Information Exposure Through Sent Data). Version 0.315.4 includes a patch that resolves this issue.
Potential Impact
Sensitive information such as authorization tokens can be exposed to unauthorized actors through browser history, shared URLs, and server or proxy logs. This exposure could potentially lead to information disclosure but does not directly impact integrity or availability. The CVSS score of 3.1 reflects a low impact severity.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-13T06:54:34.219Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a218ccee29bf47b50ad1bb3
Added to database: 6/4/2026, 2:33:50 PM
Last enriched: 6/4/2026, 2:48:38 PM
Last updated: 6/4/2026, 4:00:46 PM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.