# RubyGems Deserialization of Untrusted Data vulnerability

Advisory record · `GHSA-qj2w-mw2r-pv39`

- **Identifiers:** `GHSA-qj2w-mw2r-pv39` · `CVE-2018-1000074`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 14 May 2022
- **Updated:** 12 Mar 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 May 2022, 01:01 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `rubygems-update` (RubyGems): affected `<2.7.6`; fixed in `2.7.6`
- `org.jruby:jruby-stdlib` (Maven): affected `<9.1.16.0`; fixed in `9.1.16.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> rubygems-update before 2.7.6 has a deserialization of untrusted data flaw in the owner command that can lead to code execution. A victim must run the gem owner command on a gem containing a specially crafted YAML file. Upgrade rubygems-update to 2.7.6, or jruby-stdlib to 9.1.16.0.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.8 High, CVSS 3.0: `CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.029, the 86th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:13 UTC: First seen by agentprime
- 31 Oct 2026, 15:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qj2w-mw2r-pv39)

## Sources

- [GitHub Advisory Database: GHSA-qj2w-mw2r-pv39](https://github.com/advisories/GHSA-qj2w-mw2r-pv39)
- [OSV: GHSA-qj2w-mw2r-pv39](https://osv.dev/vulnerability/GHSA-qj2w-mw2r-pv39)
- <https://nvd.nist.gov/vuln/detail/CVE-2018-1000074>
- <https://github.com/jruby/jruby/commit/0b06b48ab4432237ce5fc1bef47f2c6bcf7843f7>
- <https://github.com/rubygems/rubygems/commit/254e3d0ee873c008c0b74e8b8abcbdab4caa0a6d>
- <https://github.com/rubygems/rubygems/commit/5971b486d4dbb2bad5d3445b3801c456eb0ce183>
- <https://www.debian.org/security/2018/dsa-4259>
- <https://www.debian.org/security/2018/dsa-4219>
- <https://usn.ubuntu.com/3685-1>
- <https://usn.ubuntu.com/3621-2>
- <https://usn.ubuntu.com/3621-1>
- <https://lists.debian.org/debian-lts-announce/2019/05/msg00028.html>
- <https://lists.debian.org/debian-lts-announce/2018/08/msg00028.html>
- <https://lists.debian.org/debian-lts-announce/2018/04/msg00017.html>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-qj2w-mw2r-pv39>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-qj2w-mw2r-pv39/>. Everything for agents: <https://agentprime.io/llms.txt>.