Skip to main content
VulnerabilityPublished Updated

CVE-2026-104828: htmlunit-neko · Cross-site Scripting

Affects htmlunit-nekoSource CVE Database V5

0

Not known to be exploited · CVSS 7.2 High : upgrade to 5.4.0 soon.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.4.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade htmlunit-neko and org.htmlunit/htmlunit-neko to 5.4.0.

Affected software

ProductAffectedFixed in
HtmlUnithtmlunit-nekoAffected
  • <5.4.0
Fixed in
  • 5.4.0
Mavenorg.htmlunit/htmlunit-nekopkg:maven/org.htmlunit/htmlunit-nekoOther threatsAffected
  • <5.4.0
Fixed in
  • 5.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade htmlunit-neko to version 5.4.0 or later, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory. Patch status is confirmed fixed in 5.4.0.

Description

CVE-2026-104828 is a cross-site scripting (XSS) vulnerability in htmlunit-neko, an adaptation of NekoHTML used by HtmlUnit. Versions prior to 5.4.0 improperly handle TEXTAREA and TITLE element content by writing decoded character data without entity encoding. This causes entity references inside these elements to be decoded and emitted as raw markup during parse-and-serialize operations, potentially allowing attacker-controlled encoded text to become executable markup in browsers. The issue is fixed in version 5.4.0.

References

Community reviews

Loading reviews…