How severe is GHSA-mpwp-4h2m-765c?

No CVSS score has been assigned to GHSA-mpwp-4h2m-765c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mpwp-4h2m-765c?

GHSA-mpwp-4h2m-765c affects the following packages: activejob (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-mpwp-4h2m-765c?

Update activejob to 4.2.0.beta2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mpwp-4h2m-765c is resolved across your whole dependency graph.

How do I detect GHSA-mpwp-4h2m-765c in my RubyGems dependencies?

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

How do I mitigate GHSA-mpwp-4h2m-765c if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is GHSA-mpwp-4h2m-765c actively exploited in the wild?

No public exploit code has been indexed for GHSA-mpwp-4h2m-765c 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.

When was GHSA-mpwp-4h2m-765c published, and has it been updated?

GHSA-mpwp-4h2m-765c was published on January 16, 2026 and was last updated on February 3, 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

Active Job - Object injection security vulnerabilityGHSA-mpwp-4h2m-765c

GHSA-mpwp-4h2m-765c is a remote code execution vulnerability in activejob. A fix is available for activejob — see the affected versions and patch details below.

Published

Jan 16, 2026

Updated

Feb 3, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 3, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

💎activejob

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

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`activejob`	all versions	4.2.0.beta2`bundle update activejob --conservative`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for activejob, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update activejob to 4.2.0.beta2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mpwp-4h2m-765c is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-mpwp-4h2m-765c in your dependencies?

Find it across RubyGems, including transitive dependencies.

Scan my dependencies How O3 SCA works