CVE-2022-50999
Integer overflow in Nokogiri's libxml2 allows crafted XML to trigger out-of-bounds writes.
Is CVE-2022-50999 being exploited?
Not confirmed. CVE-2022-50999 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.
How severe is CVE-2022-50999?
CVE-2022-50999 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2022-50999?
Yes. A fix has been recorded for CVE-2022-50999. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2022-50999 affect?
CVE-2022-50999 affects Nokogiri < 1.13.5, Ruby apps using packaged libxml2, Applications parsing untrusted XML. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2022-50999?
Upgrade Nokogiri to >=1.13.5; validate and limit XML input sizes.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Processing multi-GB crafted XML can trigger buffer overflows enabling information disclosure, memory corruption, potential remote code execution or denial of service.
Patch when possible