CVE-2025-27407

CRITICALNVD 9.09.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2025-03-12. NVD baseline CVSS 9.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-7224 (ENISA EUVD) · GHSA-q92j-grw3-h492 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3.1%CVSS: 9.0Exploit: None knownExposed services: Not assessed

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.0CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation3.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
3.1%
EPSS %ILE
87th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.

EG Severity
9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
3.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 12, 2025

Last Modified

April 15, 2026

Advisory Details (10)

Auto-updated May 21, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

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
Web page

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrubygem-graphql-0:1.13.24-1.el9sat2025-05-06redhat
redhatrubygem-graphql-0:1.13.24-1.el8sat2025-04-01redhat
rubygemsgraphql @ 2.4.13 (fixes >= 2.4.0, < 2.4.13)—ghsa
rubygemsgraphql @ 2.3.21 (fixes >= 2.3.0, < 2.3.21)—ghsa
rubygemsgraphql @ 2.0.32 (fixes >= 2.0.0, < 2.0.32)—ghsa
rubygemsgraphql @ 1.13.24 (fixes >= 1.13.0, < 1.13.24)—ghsa
rubygemsgraphql @ 1.12.25 (fixes >= 1.12.0, < 1.12.25)—ghsa
rubygemsgraphql @ 2.1.15 (fixes >= 2.1.0, < 2.1.15)—ghsa
rubygemsgraphql @ 1.11.11 (fixes >= 1.11.5, < 1.11.11)—ghsa
rubygemsgraphql @ 2.2.17 (fixes >= 2.2.0, < 2.2.17)—ghsa

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-graphql1.11.10-1, 1.11.4-1, 1.11.8-1, 1.11.8-2, 1.11.8-3
  • every version up to 1.11.12-0+deb11u1: fixed in 1.11.12-0+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-graphql1.13.15-1 ... 2.6.9-1 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-graphql—
  • every version up to 2.2.17-1: fixed in 2.2.17-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-graphql—
  • every version up to 2.2.17-1: fixed in 2.2.17-1
—
RubyGems(1)
PackageVulnerable rangeFix by version rangeDependents
graphql1.11.10 ... 1.11.9 (6 versions)
  • 2.4.0 up to 2.4.13: fixed in 2.4.13
  • 2.3.0 up to 2.3.21: fixed in 2.3.21
  • 2.2.0 up to 2.2.17: fixed in 2.2.17
  • 2.1.0 up to 2.1.15: fixed in 2.1.15
  • 2.0.0 up to 2.0.32: fixed in 2.0.32
  • 1.13.0 up to 1.13.24: fixed in 1.13.24
  • 1.12.0 up to 1.12.25: fixed in 1.12.25
  • 1.11.5 up to 1.11.11: fixed in 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 23× in last 7d / 76× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 312 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 212 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:49 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  2. 2026-11-13 11:43 UTCEchelonGraph re-scored
  3. 2026-11-13 11:43 UTCVendor advisory
  4. 2026-11-13 11:43 UTCGHSA enrichmentGHSA-q92j-grw3-h492 · GitHub severity CRITICAL · GitHub CVSS 9.0
  5. 2026-11-12 16:32 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  6. 2026-11-12 13:41 UTCEchelonGraph re-scored
  7. 2026-11-12 13:41 UTCVendor advisory
  8. 2026-11-12 13:41 UTCGHSA enrichmentGHSA-q92j-grw3-h492 · GitHub severity CRITICAL · GitHub CVSS 9.0
  9. 2026-11-11 16:36 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  10. 2026-11-11 15:39 UTCVendor advisory
  11. 2026-11-11 15:39 UTCGHSA enrichmentGHSA-q92j-grw3-h492 · GitHub severity CRITICAL · GitHub CVSS 9.0
  12. 2026-11-10 17:37 UTCEchelonGraph re-scored
  13. 2026-11-10 17:37 UTCVendor advisory
  14. 2026-11-10 17:37 UTCGHSA enrichmentGHSA-q92j-grw3-h492 · GitHub severity CRITICAL · GitHub CVSS 9.0
  15. 2026-11-10 16:40 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  16. 2026-11-09 19:35 UTCEchelonGraph re-scored
  17. 2026-11-09 19:35 UTCVendor advisory
  18. 2026-11-09 19:35 UTCGHSA enrichmentGHSA-q92j-grw3-h492 · GitHub severity CRITICAL · GitHub CVSS 9.0
  19. 2026-11-09 16:32 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  20. 2026-11-08 21:34 UTCEchelonGraph re-scored
  21. 2026-11-08 21:34 UTCVendor advisory
  22. 2026-11-08 21:34 UTCGHSA enrichmentGHSA-q92j-grw3-h492 · GitHub severity CRITICAL · GitHub CVSS 9.0
  23. 2026-11-08 16:36 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  24. 2026-11-07 23:32 UTCEchelonGraph re-scored
  25. 2026-11-07 23:32 UTCVendor advisory
Show 75 more
  1. 2026-11-07 23:32 UTCGHSA enrichmentGHSA-q92j-grw3-h492 · GitHub severity CRITICAL · GitHub CVSS 9.0
  2. 2026-11-07 16:36 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  3. 2026-11-07 01:29 UTCEchelonGraph re-scored
  4. 2026-11-07 01:29 UTCVendor advisory
  5. 2026-11-07 01:29 UTCGHSA enrichmentGHSA-q92j-grw3-h492 · GitHub severity CRITICAL · GitHub CVSS 9.0
  6. 2026-11-06 16:33 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  7. 2026-11-06 03:27 UTCEchelonGraph re-scored
  8. 2026-11-06 03:27 UTCVendor advisory
  9. 2026-11-06 03:27 UTCGHSA enrichmentGHSA-q92j-grw3-h492 · GitHub severity CRITICAL · GitHub CVSS 9.0
  10. 2026-11-05 16:35 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  11. 2026-11-05 10:55 UTCOSV refresh
  12. 2026-11-05 05:25 UTCEchelonGraph re-scored
  13. 2026-11-05 05:25 UTCVendor advisory
  14. 2026-11-05 05:25 UTCGHSA enrichmentGHSA-q92j-grw3-h492 · GitHub severity CRITICAL · GitHub CVSS 9.0
  15. 2026-11-04 16:33 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  16. 2026-11-04 07:23 UTCEchelonGraph re-scored
  17. 2026-11-04 07:23 UTCVendor advisory
  18. 2026-11-04 07:23 UTCGHSA enrichmentGHSA-q92j-grw3-h492 · GitHub severity CRITICAL · GitHub CVSS 9.0
  19. 2026-11-03 16:44 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  20. 2026-11-03 09:21 UTCEchelonGraph re-scored
  21. 2026-11-03 09:21 UTCVendor advisory
  22. 2026-11-03 09:21 UTCGHSA enrichmentGHSA-q92j-grw3-h492 · GitHub severity CRITICAL · GitHub CVSS 9.0
  23. 2026-11-02 11:19 UTCEchelonGraph re-scored
  24. 2026-11-02 11:19 UTCVendor advisory
  25. 2026-11-02 11:19 UTCGHSA enrichmentGHSA-q92j-grw3-h492 · GitHub severity CRITICAL · GitHub CVSS 9.0
  26. 2026-11-01 13:17 UTCVendor advisory
  27. 2026-11-01 13:17 UTCGHSA enrichmentGHSA-q92j-grw3-h492 · GitHub severity CRITICAL · GitHub CVSS 9.0
  28. 2026-11-01 08:08 UTCGHSA enrichmentGHSA-q92j-grw3-h492 · GitHub severity CRITICAL · GitHub CVSS 9.0
  29. 2026-11-01 08:08 UTCEchelonGraph re-scored
  30. 2026-10-31 16:31 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  31. 2026-10-31 15:14 UTCVendor advisory
  32. 2026-10-30 17:12 UTCEchelonGraph re-scored
  33. 2026-10-30 17:12 UTCVendor advisory
  34. 2026-10-30 16:32 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  35. 2026-10-29 19:09 UTCEchelonGraph re-scored
  36. 2026-10-29 19:09 UTCVendor advisory
  37. 2026-10-29 16:31 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  38. 2026-10-28 21:07 UTCEchelonGraph re-scored
  39. 2026-10-28 21:07 UTCVendor advisory
  40. 2026-10-28 16:30 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  41. 2026-10-27 23:03 UTCEchelonGraph re-scored
  42. 2026-10-27 23:03 UTCVendor advisory
  43. 2026-10-27 16:30 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  44. 2026-10-27 00:59 UTCEchelonGraph re-scored
  45. 2026-10-27 00:59 UTCVendor advisory
  46. 2026-10-26 16:29 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  47. 2026-10-25 23:12 UTCVendor advisory
  48. 2026-10-25 16:38 UTCEchelonGraph re-scored
  49. 2026-10-25 16:31 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  50. 2026-10-25 01:09 UTCEchelonGraph re-scored
  51. 2026-10-25 01:09 UTCVendor advisory
  52. 2026-10-24 16:31 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  53. 2026-10-24 03:07 UTCEchelonGraph re-scored
  54. 2026-10-24 03:07 UTCVendor advisory
  55. 2026-10-23 16:30 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  56. 2026-10-23 05:05 UTCEchelonGraph re-scored
  57. 2026-10-23 05:05 UTCVendor advisory
  58. 2026-10-22 16:32 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  59. 2026-10-22 06:59 UTCEchelonGraph re-scored
  60. 2026-10-22 06:59 UTCVendor advisory
  61. 2026-10-21 16:31 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  62. 2026-10-21 08:57 UTCEchelonGraph re-scored
  63. 2026-10-21 08:57 UTCVendor advisory
  64. 2026-10-20 16:31 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  65. 2026-10-20 10:55 UTCEchelonGraph re-scored
  66. 2026-10-20 10:55 UTCVendor advisory
  67. 2026-10-19 16:30 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  68. 2026-10-19 12:51 UTCEchelonGraph re-scored
  69. 2026-10-19 12:51 UTCVendor advisory
  70. 2026-10-18 16:30 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  71. 2026-10-18 11:20 UTCVendor advisory
  72. 2026-10-18 05:41 UTCEchelonGraph re-scored
  73. 2026-10-17 16:32 UTCEPSS rescoreEPSS 3.1% · 87th percentile
  74. 2026-10-17 13:18 UTCEchelonGraph re-scored
  75. 2026-10-17 13:18 UTCVendor advisory

Frequently asked(5)

What is CVE-2025-27407?
CVE-2025-27407 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2025-27407 published?
The CVE record for CVE-2025-27407 was published on March 12, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2025-27407 actively exploited?
CVE-2025-27407 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% probability of exploitation in the next 30 days (87th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2025-27407 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-27407 are linked in the Vendor Advisories panel on this page.

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.