## Summary 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. ## Affected Versions - Affected: `strawberry-graphql >= 0.288.4, <= 0.315.3` - Patched: 0.315.4 The vulnerable behavior was introduced by the GraphiQL URL-sharing implementation in commit `9315ef80`, first included in release `0.288.4`. ## Impact Applications that expose Strawberry'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="graphiql"` across Strawberry HTTP integrations unless disabled or replaced by the application. 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. ## Technical Details The bundled `strawberry/static/graphiql.html` template parsed URL query parameters into a `parameters` object and used those values to initialize GraphiQL state. It also updated the URL on editor changes using `history.replaceState`. Before the fix, header values were handled like shareable query text and variables: ```js const [headers, setHeaders] = React.useState(parameters.headers); function onEditHeaders(newHeaders) { setHeaders(newHeaders); updateURL({ headers: newHeaders }); } ``` This meant arbitrary header text entered into the IDE could be serialized into `?headers=...`. ## Fix The GraphiQL template no longer calls `updateURL` from `onEditHeaders`. Query and variable URL sharing remain unchanged, and existing URLs with `headers=...` can still initialize the headers editor. Header persistence via GraphiQL's own `shouldPersistHeaders: true` behavior remains enabled, so newly edited headers can still persist locally without being placed in the URL. ## Workarounds Until a patched version can be used, applications can mitigate this issue by disabling the bundled IDE in production: ```python GraphQLRouter(schema, graphql_ide=None) ``` Equivalent `graphql_ide=None` configuration is available in Strawberry's other HTTP integrations. Applications can also provide a custom GraphiQL template that does not serialize header values into the URL. ## Credits Reported by `@lpschroer`.
## Summary 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. ## Affected Versions - Affected: `strawberry-graphql >= 0.288.4, <= 0.315.3` - Patched: 0.315.4 The vulnerable behavior was introduced by the GraphiQL URL-sharing implementation in commit `9315ef80`, first included in release `0.288.4`. ## Impact Applications that expose Strawberry'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="graphiql"` across Strawberry HTTP integrations unless disabled or replaced by the application. 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. ## Technical Details The bundled `strawberry/static/graphiql.html` template parsed URL query parameters into a `parameters` object and used those values to initialize GraphiQL state. It also updated the URL on editor changes using `history.replaceState`. Before the fix, header values were handled like shareable query text and variables: ```js const [headers, setHeaders] = React.useState(parameters.headers); function onEditHeaders(newHeaders) { setHeaders(newHeaders); updateURL({ headers: newHeaders }); } ``` This meant arbitrary header text entered into the IDE could be serialized into `?headers=...`. ## Fix The GraphiQL template no longer calls `updateURL` from `onEditHeaders`. Query and variable URL sharing remain unchanged, and existing URLs with `headers=...` can still initialize the headers editor. Header persistence via GraphiQL's own `shouldPersistHeaders: true` behavior remains enabled, so newly edited headers can still persist locally without being placed in the URL. ## Workarounds Until a patched version can be used, applications can mitigate this issue by disabling the bundled IDE in production: ```python GraphQLRouter(schema, graphql_ide=None) ``` Equivalent `graphql_ide=None` configuration is available in Strawberry's other HTTP integrations. Applications can also provide a custom GraphiQL template that does not serialize header values into the URL. ## Credits Reported by `@lpschroer`.
Update strawberry-graphql to 0.315.4 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanStrawberry GraphQL: Default GraphiQL may expose HTTP headers in URLs affects strawberry-graphql (pip). Severity is low. ## Summary 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. ## Affected Versions - Affected: `strawberry-graphql >= 0.288.4, <= 0.315.3` - Patched: 0.315.4 The vulnerable behavior was introduced by the GraphiQL URL-sharing implementation in commit `9315ef80`, first included in release `0.288.4`. ## Impact Applications that expose Strawberry'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="graphiql"` across Strawberry HTTP integrations unless disabled or replaced by the application. 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. ## Technical Details The bundled `strawberry/static/graphiql.html` template parsed URL query parameters into a `parameters` object and used those values to initialize GraphiQL state. It also updated the URL on editor changes using `history.replaceState`. Before the fix, header values were handled like shareable query text and variables: ```js const [headers, setHeaders] = React.useState(parameters.headers); function onEditHeaders(newHeaders) { setHeaders(newHeaders); updateURL({ headers: newHeaders }); } ``` This meant arbitrary header text entered into the IDE could be serialized into `?headers=...`. ## Fix The GraphiQL template no longer calls `updateURL` from `onEditHeaders`. Query and variable URL sharing remain unchanged, and existing URLs with `headers=...` can still initialize the headers editor. Header persistence via GraphiQL's own `shouldPersistHeaders: true` behavior remains enabled, so newly edited headers can still persist locally without being placed in the URL. ## Workarounds Until a patched version can be used, applications can mitigate this issue by disabling the bundled IDE in production: ```python GraphQLRouter(schema, graphql_ide=None) ``` Equivalent `graphql_ide=None` configuration is available in Strawberry's other HTTP integrations. Applications can also provide a custom GraphiQL template that does not serialize header values into the URL. ## Credits Reported by `@lpschroer`.
AI coding agents often install or upgrade packages automatically in pip. A low vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| strawberry-graphqlpip | >=0.288.4,<=0.315.3 | 0.315.4 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate strawberry-graphql to 0.315.4 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanStrawberry GraphQL: Default GraphiQL may expose HTTP headers in URLs affects strawberry-graphql (pip). Severity is low. ## Summary 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. ## Affected Versions - Affected: `strawberry-graphql >= 0.288.4, <= 0.315.3` - Patched: 0.315.4 The vulnerable behavior was introduced by the GraphiQL URL-sharing implementation in commit `9315ef80`, first included in release `0.288.4`. ## Impact Applications that expose Strawberry'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="graphiql"` across Strawberry HTTP integrations unless disabled or replaced by the application. 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. ## Technical Details The bundled `strawberry/static/graphiql.html` template parsed URL query parameters into a `parameters` object and used those values to initialize GraphiQL state. It also updated the URL on editor changes using `history.replaceState`. Before the fix, header values were handled like shareable query text and variables: ```js const [headers, setHeaders] = React.useState(parameters.headers); function onEditHeaders(newHeaders) { setHeaders(newHeaders); updateURL({ headers: newHeaders }); } ``` This meant arbitrary header text entered into the IDE could be serialized into `?headers=...`. ## Fix The GraphiQL template no longer calls `updateURL` from `onEditHeaders`. Query and variable URL sharing remain unchanged, and existing URLs with `headers=...` can still initialize the headers editor. Header persistence via GraphiQL's own `shouldPersistHeaders: true` behavior remains enabled, so newly edited headers can still persist locally without being placed in the URL. ## Workarounds Until a patched version can be used, applications can mitigate this issue by disabling the bundled IDE in production: ```python GraphQLRouter(schema, graphql_ide=None) ``` Equivalent `graphql_ide=None` configuration is available in Strawberry's other HTTP integrations. Applications can also provide a custom GraphiQL template that does not serialize header values into the URL. ## Credits Reported by `@lpschroer`.
AI coding agents often install or upgrade packages automatically in pip. A low vulnerability in a dependency can be pulled into a project through a normal install or update without a human reviewing the change, expanding the blast radius from a single package to every agent workspace that depends on it.
| Package | Affected range | Fixed version |
|---|---|---|
| strawberry-graphqlpip | >=0.288.4,<=0.315.3 | 0.315.4 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL Guard