GHSA-MPWP-4H2M-765C

GHSA-MPWP-4H2M-765C is a medium-severity security vulnerability in activejob (rubygems), affecting versions < 4.2.0.beta2. It is fixed in 4.2.0.beta2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Active Job - Object injection security vulnerability

Active Job vulnerability: An Active Job bug allowed String arguments to be deserialized as if they were Global IDs, an object injection security vulnerability.

Impact

Affected versions

activejob (< 4.2.0.beta2)

Security releases

activejob → 4.2.0.beta2 (rubygems)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade activejob to 4.2.0.beta2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-MPWP-4H2M-765C? GHSA-MPWP-4H2M-765C is a medium-severity security vulnerability in activejob (rubygems), affecting versions < 4.2.0.beta2. It is fixed in 4.2.0.beta2.
  2. Which versions of activejob are affected by GHSA-MPWP-4H2M-765C? activejob (rubygems) versions < 4.2.0.beta2 is affected.
  3. Is there a fix for GHSA-MPWP-4H2M-765C? Yes. GHSA-MPWP-4H2M-765C is fixed in 4.2.0.beta2. Upgrade to this version or later.
  4. Is GHSA-MPWP-4H2M-765C exploitable, and should I be worried? Whether GHSA-MPWP-4H2M-765C is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether GHSA-MPWP-4H2M-765C is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix GHSA-MPWP-4H2M-765C? Upgrade activejob to 4.2.0.beta2 or later.

Other vulnerabilities in activejob

Stop the waste.
Protect your environment with Kodem.