<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/ghsa-q3cc-p5hm-55wj-graphql-interpreter-runtime-renders-results-from-objects-whose-authorized--y3myexcf2" -->

---
title: GHSA-q3cc-p5hm-55wj (graphql): Interpreter runtime...
description: The graphql-ruby legacy interpreter can render unauthorized objects despite failed authorization checks. When `authorized?` raises `GraphQL::UnauthorizedError`...
canonical: https://daily.dev/posts/ghsa-q3cc-p5hm-55wj-graphql-interpreter-runtime-renders-results-from-objects-whose-authorized--y3myexcf2
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: GHSA-q3cc-p5hm-55wj (graphql): Interpreter runtime renders results from objects whose `.authorized?` checks had failed | daily.dev
og:description: The graphql-ruby legacy interpreter can render unauthorized objects despite failed authorization checks. When `authorized?` raises `GraphQL::UnauthorizedError`...
og:url: https://daily.dev/posts/ghsa-q3cc-p5hm-55wj-graphql-interpreter-runtime-renders-results-from-objects-whose-authorized--y3myexcf2
og:image: https://api.daily.dev/og/posts/y3myExCF2.png
og:image:alt: GHSA-q3cc-p5hm-55wj (graphql): Interpreter runtime renders results from objects whose `.authorized?` checks had failed
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# GHSA-q3cc-p5hm-55wj (graphql): Interpreter runtime renders results from objects whose `.authorized?` checks had failed

**[RUBYLAND](https://daily.dev/sources/rubyla)** · 1 min read · 0 upvotes · 0 comments

## Summary

The graphql-ruby legacy interpreter can render unauthorized objects despite failed authorization checks. When `authorized?` raises `GraphQL::UnauthorizedError` and `Schema.unauthorized_object` returns a replacement, `Execution::Interpreter` renders the original, unauthorized object instead. Returning `false` from `authorized?` correctly renders the replacement object. The issue carries a CVSS score of 6.5 (medium) and is patched in versions 2.6.14 and later.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://rubysec.com/advisories/GHSA-q3cc-p5hm-55wj>

## Questions this post answers

### Why does graphql-ruby still return the unauthorized object when my authorized? method raises GraphQL::UnauthorizedError?

This is a known bug in the legacy Execution::Interpreter: when authorized? raises GraphQL::UnauthorizedError and Schema.unauthorized_object returns a replacement object, the interpreter incorrectly renders the original unauthorized object instead of the replacement. Returning false from authorized? works correctly. The fix is in graphql-ruby 2.6.14 and later; versions before 1.10.0 are unaffected.

_Teams patching authorization bugs like this track graphql-ruby advisories and fixes on daily.dev._

### What graphql-ruby version fixes the unauthorized object rendering bug with authorized? raising errors?

Version 2.6.14 and later patches the issue where Execution::Interpreter rendered unauthorized objects when authorized? raised GraphQL::UnauthorizedError instead of returning false. The CVSS v3.x severity score for this issue is 6.5, rated medium. Versions before 1.10.0 are not affected by this bug.

_Developers upgrading graphql-ruby to close authorization gaps can follow releases like this on daily.dev._

## Similar posts on daily.dev

- [GHSA-4rw8-495r-pf6j \(graphql\): Execution::Next renders objects whose authorized? check failed](https://daily.dev/posts/ghsa-4rw8-495r-pf6j-graphql-execution-next-renders-objects-whose-authorized-check-failed-0j2vrvyxg) · RUBYLAND · 0 upvotes · 0 comments
- [GHSA-prq8-7wvh-44qh \(oauth\): Cross-origin OAuth token-request redirects can expose signed request metadata](https://daily.dev/posts/ghsa-prq8-7wvh-44qh-oauth-cross-origin-oauth-token-request-redirects-can-expose-signed-request-me-ktjgrr4kt) · RUBYLAND · 0 upvotes · 0 comments
- [Access control for AI agents on Rails: gating SQL with Action Policy—Martian Chronicles, Evil Martians’ team blog](https://daily.dev/posts/access-control-for-ai-agents-on-rails-gating-sql-with-action-policy-martian-chronicles-evil-martia-efskld2gj) · Martian Chronicles · 0 upvotes · 1 comments
- [Permit.Absinthe 0.2: Absinthe GraphQL authorization for Elixir](https://daily.dev/posts/permit-absinthe-0-2-absinthe-graphql-authorization-for-elixir-s1buxnnlf) · Curiosum · 0 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#ruby](https://daily.dev/tags/ruby), [#graphql](https://daily.dev/tags/graphql), [#authorization](https://daily.dev/tags/authorization)

[View this post on daily.dev](https://daily.dev/posts/ghsa-q3cc-p5hm-55wj-graphql-interpreter-runtime-renders-results-from-objects-whose-authorized--y3myexcf2)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"GHSA-q3cc-p5hm-55wj (graphql): Interpreter runtime renders results from objects whose `.authorized?` checks had failed","url":"https://daily.dev/posts/ghsa-q3cc-p5hm-55wj-graphql-interpreter-runtime-renders-results-from-objects-whose-authorized--y3myexcf2","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/ghsa-q3cc-p5hm-55wj-graphql-interpreter-runtime-renders-results-from-objects-whose-authorized--y3myexcf2"},"datePublished":"2026-11-01T19:21:43.849Z","dateModified":"2026-11-01T19:22:04.910Z","description":"The graphql-ruby legacy interpreter can render unauthorized objects despite failed authorization checks. When `authorized?` raises `GraphQL::UnauthorizedError`...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5fa7bf38a8a9c178c1d458f9f735556c?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/5fa7bf38a8a9c178c1d458f9f735556c?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"RUBYLAND","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"RUBYLAND","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/rubyla","url":"https://daily.dev/sources/rubyla"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/ghsa-q3cc-p5hm-55wj-graphql-interpreter-runtime-renders-results-from-objects-whose-authorized--y3myexcf2","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,ruby,graphql,authorization","timeRequired":"PT1M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"RUBYLAND","item":"https://daily.dev/sources/rubyla"},{"@type":"ListItem","position":3,"name":"GHSA-q3cc-p5hm-55wj (graphql): Interpreter runtime renders results from objects whose `.authorized?` checks had failed"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/ghsa-q3cc-p5hm-55wj-graphql-interpreter-runtime-renders-results-from-objects-whose-authorized--y3myexcf2#faq","mainEntity":[{"@type":"Question","name":"Why does graphql-ruby still return the unauthorized object when my authorized? method raises GraphQL::UnauthorizedError?","acceptedAnswer":{"@type":"Answer","text":"This is a known bug in the legacy Execution::Interpreter: when authorized? raises GraphQL::UnauthorizedError and Schema.unauthorized_object returns a replacement object, the interpreter incorrectly renders the original unauthorized object instead of the replacement. Returning false from authorized? works correctly. The fix is in graphql-ruby 2.6.14 and later; versions before 1.10.0 are unaffected. Teams patching authorization bugs like this track graphql-ruby advisories and fixes on daily.dev."}},{"@type":"Question","name":"What graphql-ruby version fixes the unauthorized object rendering bug with authorized? raising errors?","acceptedAnswer":{"@type":"Answer","text":"Version 2.6.14 and later patches the issue where Execution::Interpreter rendered unauthorized objects when authorized? raised GraphQL::UnauthorizedError instead of returning false. The CVSS v3.x severity score for this issue is 6.5, rated medium. Versions before 1.10.0 are not affected by this bug. Developers upgrading graphql-ruby to close authorization gaps can follow releases like this on daily.dev."}}]}
```

