Skip to content

graphql allows remote code execution when loading a crafted GraphQL schema

Critical severity GitHub Reviewed Published Mar 12, 2025 in rmosolgo/graphql-ruby • Updated Mar 12, 2025

Package

bundler graphql (RubyGems)

Affected versions

>= 2.4.0, < 2.4.13
>= 2.3.0, < 2.3.21
>= 2.2.10, < 2.2.17
>= 2.0.0, < 2.0.32
>= 1.13.0, < 1.13.24
>= 1.12.0, < 1.12.25
>= 2.1.0, < 2.1.15
>= 1.11.5, < 1.11.11

Patched versions

2.4.13
2.3.21
2.2.17
2.0.32
1.13.24
1.12.25
2.1.15
1.11.11

Description

Summary

Loading a malicious schema definition in GraphQL::Schema.from_introspection (or GraphQL::Schema::Loader.load) can result in remote code execution. Any system which loads a schema by JSON from an untrusted source is vulnerable, including those that use GraphQL::Client to load external schemas via GraphQL introspection.

References

@rmosolgo rmosolgo published to rmosolgo/graphql-ruby Mar 12, 2025
Published by the National Vulnerability Database Mar 12, 2025
Published to the GitHub Advisory Database Mar 12, 2025
Reviewed Mar 12, 2025
Last updated Mar 12, 2025

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

EPSS score

Weaknesses

CVE ID

CVE-2025-27407

GHSA ID

GHSA-q92j-grw3-h492

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.