# Nokogiri vulnerable to libxslt protection mechanism bypass

Advisory record · `GHSA-qxcg-xjjg-66mj`

- **Identifiers:** `GHSA-qxcg-xjjg-66mj` · `CVE-2019-11068`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **Published:** 13 May 2022
- **Updated:** 9 Jun 2026
- **Reviewed by a person:** No

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

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `nokogiri` (RubyGems): affected `<1.10.3`; fixed in `1.10.3`

## 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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.052, the 92nd percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 13 May 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-qxcg-xjjg-66mj](https://github.com/advisories/GHSA-qxcg-xjjg-66mj)
- [OSV: GHSA-qxcg-xjjg-66mj](https://osv.dev/vulnerability/GHSA-qxcg-xjjg-66mj)
- <https://nvd.nist.gov/vuln/detail/CVE-2019-11068>
- <https://github.com/sparklemotion/nokogiri/issues/1892>
- <https://github.com/sparklemotion/nokogiri/pull/1898>
- <https://github.com/sparklemotion/nokogiri/commit/fe034aedcc59b566740567d621843731686676b9>
- <https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html>
- <https://usn.ubuntu.com/3947-2>
- <https://usn.ubuntu.com/3947-1>
- <https://security.netapp.com/advisory/ntap-20191017-0001>
- <https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SK4YNISS22MJY22YX5I6V2U63QZAUEHA>
- <https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GCOAX2IHUMKCM3ILHTMGLHCDSBTLP2JU>
- <https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/36TEYN37XCCKN2XUMRTBBW67BPNMSW4K>
- <https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SK4YNISS22MJY22YX5I6V2U63QZAUEHA>

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-qxcg-xjjg-66mj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-qxcg-xjjg-66mj/>. Everything for agents: <https://agentprime.io/llms.txt>.
