How severe is GHSA-7rrm-v45f-jp64?

No CVSS score has been assigned to GHSA-7rrm-v45f-jp64 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7rrm-v45f-jp64?

GHSA-7rrm-v45f-jp64 affects the following packages: nokogiri (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-7rrm-v45f-jp64?

Update nokogiri to 1.11.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7rrm-v45f-jp64 is resolved across your whole dependency graph.

How do I detect GHSA-7rrm-v45f-jp64 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nokogiri. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-7rrm-v45f-jp64 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-7rrm-v45f-jp64?

O3 pinpoints whether GHSA-7rrm-v45f-jp64 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-7rrm-v45f-jp64 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7rrm-v45f-jp64 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 type of vulnerability is GHSA-7rrm-v45f-jp64?

GHSA-7rrm-v45f-jp64 is classified as Buffer Overflow (CWE-119). 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-7rrm-v45f-jp64 published, and has it been updated?

GHSA-7rrm-v45f-jp64 was published on May 17, 2021 and was last updated on August 27, 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

GHSA-7rrm-v45f-jp64

Fix: sparklemotion/nokogiri@9b90a88

GHSA-7rrm-v45f-jp64 is a Buffer Overflow vulnerability in nokogiri. O3 Security confirms whether GHSA-7rrm-v45f-jp64 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Nokogiri updates packaged dependency on libxml2 from 2.9.10 to 2.9.12

Also known asCVE-2021-47996

Published

May 17, 2021

Updated

Aug 27, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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-7rrm-v45f-jp64.

Real-World Exposure

1 pkg affected

💎nokogiri

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

Summary

Nokogiri v1.11.4 updates the vendored libxml2 from v2.9.10 to v2.9.12 which addresses:

CVE-2019-20388 (Medium severity)
CVE-2020-24977 (Medium severity)
CVE-2021-3517 (Medium severity)
CVE-2021-3518 (Medium severity)
CVE-2021-3537 (Low severity)
CVE-2021-3541 (Low severity)

Note that two additional CVEs were addressed upstream but are not relevant to this release. CVE-2021-3516 via xmllint is not present in Nokogiri, and CVE-2020-7595 has been patched in Nokogiri since v1.10.8 (see #1992).

Please note that this advisory only applies to the CRuby implementation of Nokogiri < 1.11.4, and only if the packaged version of libxml2 is being used. If you've overridden defaults at installation time to use system libraries instead of packaged libraries, you should instead pay attention to your distro's libxml2 release announcements.

Mitigation

Upgrade to Nokogiri >= 1.11.4.

Impact

I've done a brief analysis of the published CVEs that are addressed in this upstream release. The libxml2 maintainers have not released a canonical set of CVEs, and so this list is pieced together from secondary sources and may be incomplete.

All information below is sourced from security.archlinux.org, which appears to have the most up-to-date information as of this analysis.