How severe is GHSA-mx5j-mp4f-g8jg?

GHSA-mx5j-mp4f-g8jg has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-mx5j-mp4f-g8jg?

GHSA-mx5j-mp4f-g8jg affects the following packages: savon (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-mx5j-mp4f-g8jg?

Update savon to 2.17.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mx5j-mp4f-g8jg is resolved across your whole dependency graph.

How do I detect GHSA-mx5j-mp4f-g8jg in my RubyGems dependencies?

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

How do I mitigate GHSA-mx5j-mp4f-g8jg 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 GHSA-mx5j-mp4f-g8jg actively exploited in the wild?

No public exploit code has been indexed for GHSA-mx5j-mp4f-g8jg 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 GHSA-mx5j-mp4f-g8jg?

GHSA-mx5j-mp4f-g8jg has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 53th 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 GHSA-mx5j-mp4f-g8jg?

GHSA-mx5j-mp4f-g8jg 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 GHSA-mx5j-mp4f-g8jg published, and has it been updated?

GHSA-mx5j-mp4f-g8jg was published on July 31, 2026 and was last updated on July 31, 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

HIGH severity

Savon::Model evaluates WSDL operation names as Ruby sourceGHSA-mx5j-mp4f-g8jg

HIGHFix: savonrb/savon@8f22eb5

GHSA-mx5j-mp4f-g8jg is a high-severity (CVSS 8.1) Code Injection vulnerability in savon. A fix is available for savon — see the affected versions and patch details below.

Also known asCVE-2026-53510

Published

Jul 31, 2026

Updated

Jul 31, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 29, 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 GHSA-mx5j-mp4f-g8jg.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs53th percentile — riskier than 53% 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

1 pkg affected

💎savon

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

Impact

Savon::Model generated SOAP operation methods by interpolating operation names into Ruby source passed to module_eval. An attacker who can control the operation names of a WSDL, can inject Ruby code that executes in the application process. This affects only the .all_operations class method provided by Savon::Model to automatically register all operations provided by the WSDL. Configuring Savon::Model with trusted operation names via .operations is safe.

Patches

Patched in Savon 2.17.2.

Users should upgrade to 2.17.2 or later.

Workarounds

Avoid .all_operations for untrusted WSDL documents. Use .operations with trusted operation names instead.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`savon`	≥ 0.9.8&&< 2.17.2	2.17.2`bundle update savon --conservative`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for savon, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update savon to 2.17.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mx5j-mp4f-g8jg 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.

Frequently Asked Questions

### Impact `Savon::Model` generated SOAP operation methods by interpolating operation names into Ruby source passed to `module_eval`. An attacker who can control the operation names of a WSDL, can inject Ruby code that executes in the application process. This affects only the `.all_operations` class method provided by `Savon::Model` to automatically register all operations provided by the WSDL. Configuring `Savon::Model` with trusted operation names via `.operations` is safe. ### Patches Patched in Savon 2.17.2. Users should upgrade to 2.17.2 or later. ### Workarounds Avoid `.all_operat