CVE-2025-27407

CRITICALNVD 9.09.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under NVD CVSS v3. EPSS exploit probability: 1.4%, top 20% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 3%CVSS: 9.0Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.0
EG Score
9.0(medium)
EPSS
85.1%
KEV
Not listed

Published

March 12, 2025

Last Modified

April 15, 2026

Advisory Details (10)

Auto-updated May 21, 2026
Patch available. Sources: github.
github Patch Available

Remote code execution when loading a crafted GraphQL schema · Advisory · rmosolgo/graphql-ruby · GitHub

https://github.com/rmosolgo/graphql-ruby/security/advisories/GHSA-q92j-grw3-h492
generic

Merge commit from fork · rmosolgo/graphql-ruby@e3b33ac · GitHub

https://github.com/rmosolgo/graphql-ruby/commit/e3b33ace05391da2871c75ab4d3b66e29133b367
generic

Merge commit from fork · rmosolgo/graphql-ruby@d1117ae · GitHub

https://github.com/rmosolgo/graphql-ruby/commit/d1117ae0361d9ed67e0795b07f5c3e98e62f3c7c
generic

Merge commit from fork · rmosolgo/graphql-ruby@d096328 · GitHub

https://github.com/rmosolgo/graphql-ruby/commit/d0963289e0dab4ea893bbecf12bb7d89294957bb
generic

Merge commit from fork · rmosolgo/graphql-ruby@6eca16b · GitHub

https://github.com/rmosolgo/graphql-ruby/commit/6eca16b9fa553aa957099a30dbde64ddcdac52ca
generic

Merge commit from fork · rmosolgo/graphql-ruby@5c5a7b9 · GitHub

https://github.com/rmosolgo/graphql-ruby/commit/5c5a7b9a9bdce143be048074aea50edb7bb747be
generic

Merge commit from fork · rmosolgo/graphql-ruby@2d2f4ed · GitHub

https://github.com/rmosolgo/graphql-ruby/commit/2d2f4ed1f79472f8eed29c864b039649e1de238f
generic

Merge commit from fork · rmosolgo/graphql-ruby@28233b1 · GitHub

https://github.com/rmosolgo/graphql-ruby/commit/28233b16c0eb9d0fb7808f4980e061dc7507c4cd
generic

GitHub - github-community-projects/graphql-client: A Ruby library for declaring, composing and executing GraphQL queries · GitHub

https://github.com/github-community-projects/graphql-client
generic

GitLab release notes | GitLab Docs

https://about.gitlab.com/releases/2025/03/12/patch-release-gitlab-17-9-2-released

Vendor Advisories for CVE-2025-27407(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrubygem-graphql-0:1.13.24-1.el9sat2025-05-06redhat
redhatrubygem-graphql-0:1.13.24-1.el8sat2025-04-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
RubyGems(1)
PackageVulnerable rangeFixed inDependents
graphql1.11.10 ... 1.11.9 (6 versions)1.11.11—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:26 UTCEPSS rescore
  3. 2026-07-06 02:22 UTCEPSS rescore
  4. 2026-07-05 02:30 UTCEPSS rescore
  5. 2026-07-04 06:30 UTCEPSS rescore
  6. 2026-07-02 17:01 UTCEPSS rescore
  7. 2026-07-01 15:06 UTCEPSS rescore
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 23:21 UTCEPSS rescore
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-28 14:07 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 04:55 UTCEPSS rescore
  14. 2026-06-28 04:55 UTCEPSS rescore
  15. 2026-06-27 03:08 UTCEPSS rescore
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-24 14:04 UTCEPSS rescore
  19. 2026-06-24 14:04 UTCEPSS rescore
  20. 2026-06-23 21:32 UTCEPSS rescore
  21. 2026-06-23 21:32 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-22 00:25 UTCOSV refresh
  25. 2026-06-21 14:56 UTCEPSS rescore
Show 70 more
  1. 2026-06-21 14:56 UTCEPSS rescore
  2. 2026-06-21 01:59 UTCEPSS rescore
  3. 2026-06-21 01:59 UTCEPSS rescore
  4. 2026-06-19 19:25 UTCEPSS rescore
  5. 2026-06-19 19:25 UTCEPSS rescore
  6. 2026-06-18 17:52 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-17 17:52 UTCEPSS rescore
  9. 2026-06-16 17:52 UTCEPSS rescore
  10. 2026-06-16 17:52 UTCEPSS rescore
  11. 2026-06-15 17:48 UTCEPSS rescore
  12. 2026-06-14 23:17 UTCEPSS rescore
  13. 2026-06-13 23:00 UTCEPSS rescore
  14. 2026-06-13 23:00 UTCEPSS rescore
  15. 2026-06-12 23:11 UTCEPSS rescore
  16. 2026-06-11 13:59 UTCEPSS rescore
  17. 2026-06-10 22:18 UTCEPSS rescore
  18. 2026-06-10 13:22 UTCEPSS rescore
  19. 2026-06-08 14:16 UTCEPSS rescore
  20. 2026-06-08 14:16 UTCEPSS rescore
  21. 2026-06-07 15:24 UTCEPSS rescore
  22. 2026-06-07 15:24 UTCEPSS rescore
  23. 2026-06-06 13:47 UTCEPSS rescore
  24. 2026-06-06 13:47 UTCEPSS rescore
  25. 2026-06-05 22:46 UTCEPSS rescore
  26. 2026-06-05 22:46 UTCEPSS rescore
  27. 2026-06-05 06:10 UTCEPSS rescore
  28. 2026-06-05 06:10 UTCEPSS rescore
  29. 2026-06-04 13:12 UTCEPSS rescore
  30. 2026-06-04 13:11 UTCEPSS rescore
  31. 2026-06-03 16:09 UTCOSV refresh
  32. 2026-06-02 20:12 UTCEPSS rescore
  33. 2026-06-01 13:51 UTCEPSS rescore
  34. 2026-06-01 13:51 UTCEPSS rescore
  35. 2026-05-31 22:30 UTCEPSS rescore
  36. 2026-05-31 22:30 UTCEPSS rescore
  37. 2026-05-31 00:16 UTCEPSS rescore
  38. 2026-05-31 00:16 UTCEPSS rescore
  39. 2026-05-29 13:44 UTCEPSS rescore
  40. 2026-05-28 13:44 UTCEPSS rescore
  41. 2026-05-28 13:44 UTCEPSS rescore
  42. 2026-05-28 13:44 UTCEPSS rescore
  43. 2026-05-28 13:44 UTCEPSS rescore
  44. 2026-05-27 13:40 UTCEPSS rescore
  45. 2026-05-27 13:40 UTCEPSS rescore
  46. 2026-05-27 13:40 UTCEPSS rescore
  47. 2026-05-27 13:40 UTCEPSS rescore
  48. 2026-05-27 13:40 UTCEPSS rescore
  49. 2026-05-26 13:43 UTCEPSS rescore
  50. 2026-05-26 13:43 UTCEPSS rescore
  51. 2026-05-26 13:43 UTCEPSS rescore
  52. 2026-05-26 13:43 UTCEPSS rescore
  53. 2026-05-26 07:18 UTCEPSS rescore
  54. 2026-05-26 07:18 UTCEPSS rescore
  55. 2026-05-26 07:18 UTCEPSS rescore
  56. 2026-05-26 07:18 UTCEPSS rescore
  57. 2026-05-23 15:20 UTCEPSS rescore
  58. 2026-05-23 00:09 UTCEG score recompute
  59. 2026-05-22 21:16 UTCEPSS rescore
  60. 2026-05-22 21:16 UTCEPSS rescore
  61. 2026-05-21 22:42 UTCEPSS rescore
  62. 2026-05-21 16:42 UTCEG score recompute
  63. 2026-05-21 16:42 UTCVendor advisory
  64. 2026-05-20 11:21 UTCEPSS rescore
  65. 2026-05-20 11:21 UTCEPSS rescore
  66. 2026-05-20 11:21 UTCEPSS rescore
  67. 2026-05-20 11:21 UTCEPSS rescore
  68. 2026-05-20 11:21 UTCEPSS rescore
  69. 2026-05-20 11:03 UTCOSV refresh
  70. 2026-05-18 21:31 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-27407?
CVE-2025-27407 is a critical vulnerability published on March 12, 2025. 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…
When was CVE-2025-27407 disclosed?
CVE-2025-27407 was first published in the National Vulnerability Database on March 12, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-27407 actively exploited?
CVE-2025-27407 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 85.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-27407?
CVE-2025-27407 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2025-27407?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-27407, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-27407

Explore →

Is Your Infrastructure Affected by CVE-2025-27407?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs