https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 21:12:11 +0000 https://cve.radiocsirt.org/vuln/cve-2026-45739 <p><strong>Affected:</strong> strawberry-graphql strawberry</p> <p>Strawberry GraphQL is a library for creating GraphQL APIs. In versions 0.288.4 through 0.315.3, Strawberry&#39;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 &lt;token&gt;`, 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.</p> <p><strong>Affected:</strong> strawberry-graphql strawberry</p> <p>Strawberry GraphQL is a library for creating GraphQL APIs. In versions 0.288.4 through 0.315.3, Strawberry&#39;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 &lt;token&gt;`, 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.</p> https://cve.radiocsirt.org/vuln/cve-2026-45739 https://cve.radiocsirt.org/vuln/ghsa-x97m-qp5c-w9xj <p><strong>Affected:</strong> PyPI: strawberry-graphql</p> <p>## Summary</p> <p>Strawberry&#39;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 &lt;token&gt;`, the value could become visible in browser history, copied links, and server/proxy/CDN access logs after a page reload or shared request.</p> <p>## Affected Versions</p> <p>- Affected: `strawberry-graphql &gt;= 0.288.4, &lt;= 0.315.3` - Patched: 0.315.4</p> <p>The vulnerable behavior was introduced by the GraphiQL URL-sharing implementation in commit `9315ef80`, first included in release `0.288.4`.</p> <p>## Impact</p> <p>Applications that expose Strawberry&#39;s default GraphiQL IDE may leak sensitive HTTP header values entered by users into the GraphiQL headers editor. The default IDE is enabled by `graphql_ide=&#34;graphiql&#34;` across Strawberry HTTP integrations unless disabled or replaced by the application.</p> <p>The exposure is limited to the browser-based IDE. GraphQL query execution is not affected, and this issue does not allow an attacker to directly execute operations or bypass authorization. Practical exploitation requires a user to enter a secret into the GraphiQL headers editor and then expose the resulting URL, for example by refreshing the page, copying the URL, sharing the URL, or causing the URL to be recorded by logging infrastructure.</p> <p>## Technical Details</p> <p>The bundled `strawberry/static/graphiql.html` template parsed URL query parameters into a `parameters` object and used those values to initiali…</p> <p><strong>Affected:</strong> PyPI: strawberry-graphql</p> <p>## Summary</p> <p>Strawberry&#39;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 &lt;token&gt;`, the value could become visible in browser history, copied links, and server/proxy/CDN access logs after a page reload or shared request.</p> <p>## Affected Versions</p> <p>- Affected: `strawberry-graphql &gt;= 0.288.4, &lt;= 0.315.3` - Patched: 0.315.4</p> <p>The vulnerable behavior was introduced by the GraphiQL URL-sharing implementation in commit `9315ef80`, first included in release `0.288.4`.</p> <p>## Impact</p> <p>Applications that expose Strawberry&#39;s default GraphiQL IDE may leak sensitive HTTP header values entered by users into the GraphiQL headers editor. The default IDE is enabled by `graphql_ide=&#34;graphiql&#34;` across Strawberry HTTP integrations unless disabled or replaced by the application.</p> <p>The exposure is limited to the browser-based IDE. GraphQL query execution is not affected, and this issue does not allow an attacker to directly execute operations or bypass authorization. Practical exploitation requires a user to enter a secret into the GraphiQL headers editor and then expose the resulting URL, for example by refreshing the page, copying the URL, sharing the URL, or causing the URL to be recorded by logging infrastructure.</p> <p>## Technical Details</p> <p>The bundled `strawberry/static/graphiql.html` template parsed URL query parameters into a `parameters` object and used those values to initiali…</p> https://cve.radiocsirt.org/vuln/ghsa-x97m-qp5c-w9xj