How severe is CVE-2025-27407?

CVE-2025-27407 has a CVSS score of 9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-27407?

CVE-2025-27407 affects the following packages: graphql (RubyGems), graphql (RubyGems), graphql (RubyGems), graphql (RubyGems), graphql (RubyGems), graphql (RubyGems), graphql (RubyGems), graphql (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2025-27407?

Update graphql to 2.4.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-27407 is resolved across your whole dependency graph.

How do I detect CVE-2025-27407 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for graphql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-27407 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2025-27407 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-27407 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-27407?

CVE-2025-27407 has an EPSS (Exploit Prediction Scoring System) score of 3.1%, placing it in the 88th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-27407?

CVE-2025-27407 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-27407 published, and has it been updated?

CVE-2025-27407 was published on March 12, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎

💎 RubyGems

Not in CISA KEV

CRITICAL severity

CVE-2025-27407 — graphql

CRITICALFix: rmosolgo/graphql-ruby@28233b1

CVE-2025-27407 is a critical-severity (CVSS 9) Code Injection vulnerability in graphql. A fix is available for graphql — see the affected versions and patch details below.

Remote code execution when loading a crafted GraphQL schema

Also known asGHSA-q92j-grw3-h492

Published

Mar 12, 2025

Updated

Oct 28, 2026

Affected

8 pkgs

Patched

8 / 8

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-27407.

EPSS Exploitation Probability

via FIRST.org ↗

3.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

8 pkgs affected

💎graphql💎graphql💎graphql💎graphql💎graphql💎graphql💎graphql💎graphql

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

graphql-ruby is a Ruby implementation of GraphQL. Starting in version 1.11.5 and prior to versions 1.11.8, 1.12.25, 1.13.24, 2.0.32, 2.1.14, 2.2.17, and 2.3.21, 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. Versions 1.11.8, 1.12.25, 1.13.24, 2.0.32, 2.1.14, 2.2.17, and 2.3.21 contain a patch for the issue.

Affected Packages

8 total 8 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`graphql`	≥ 2.4.0&&< 2.4.13	2.4.13`bundle update graphql --conservative`
💎RubyGems	`graphql`	≥ 2.3.0&&< 2.3.21	2.3.21`bundle update graphql --conservative`
💎RubyGems	`graphql`	≥ 2.2.0&&< 2.2.17	2.2.17`bundle update graphql --conservative`
💎RubyGems	`graphql`	≥ 2.1.0&&< 2.1.15	2.1.15`bundle update graphql --conservative`
💎RubyGems	`graphql`	≥ 2.0.0&&< 2.0.32	2.0.32`bundle update graphql --conservative`
💎RubyGems	`graphql`	≥ 1.13.0&&< 1.13.24	1.13.24`bundle update graphql --conservative`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for graphql, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update graphql to 2.4.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-27407 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability is marked as Important rather than Critical because interaction with the vulnerable GraphQL library is restricted to only authenticated users in Red Hat Satellite. Satellite does not dynamically load schemas from external sources, further reducing the feasibility of exploitation.

Workaround published by Red Hat

A successful exploitation of this flaw requires GraphQL schema loading. Limiting the schema loading to trusted or authenticated users will limit the impact of the vulnerability. Coupling that with a strict input validation for all GraphQL schema being loaded would reduce the risk of a successful attack and cover as a possible mitigation strategy for this vulnerability.

Source: Red Hat security advisory for CVE-2025-27407 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Satellite 6.14 for RHEL 8	`rubygem-graphql-0:1.13.24-1.el8sat`	RHSA-2025:3492
Red Hat Satellite 6.15 for RHEL 8	`rubygem-graphql-0:1.13.24-1.el8sat`	RHSA-2025:3491
Red Hat Satellite 6.16 for RHEL 8	`rubygem-graphql-0:1.13.24-1.el8sat`	RHSA-2025:3490
Red Hat Satellite 6.17 for RHEL 9	`rubygem-graphql-0:1.13.24-1.el9sat`	RHSA-2025:4576

Frequently Asked Questions

graphql-ruby is a Ruby implementation of GraphQL. Starting in version 1.11.5 and prior to versions 1.11.8, 1.12.25, 1.13.24, 2.0.32, 2.1.14, 2.2.17, and 2.3.21, 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. Versions 1.11.8, 1.12.25, 1.13.24, 2.0.32, 2.1.14, 2.2.17, and 2.3.21 contain a patch for the issue.

O3 Security · Impact-Aware SCA

Is CVE-2025-27407 in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works