CVE-2022-29546 is a high-severity (CVSS 7.5) vulnerability in net.sourceforge.htmlunit:neko-htmlunit. A fix is available for net.sourceforge.htmlunit:neko-htmlunit — see the affected versions and patch details below.
OutOfMemory Exception by specifically crafted processing instruction in NekoHtml Parser
Exploitation Status
No confirmed exploitation observed yet
- 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 CVE-2022-29546.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
net.sourceforge.htmlunit:neko-htmlunitReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
NekoHtml Parser suffers from a denial of service vulnerability on versions 2.60.0 and below. A specifically crafted input regarding the parsing of processing instructions leads to heap memory consumption. Please update to version 2.61.0.
For more information
If you have any questions or comments about this advisory:
- Open an issue in https://github.com/HtmlUnit/htmlunit-neko
- Email us at [rbri at rbri.de]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | net.sourceforge.htmlunit:neko-htmlunit | all versions | 2.61.0net.sourceforge.htmlunit:neko-htmlunit:2.61.0 |
Affected Products
htmlunithtmlunitDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.sourceforge.htmlunit:neko-htmlunit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update net.sourceforge.htmlunit:neko-htmlunit to 2.61.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-29546 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2022-29546 in your dependencies?
Find it across Maven, including transitive dependencies.