What is CVE-2025-66021?

CVE-2025-66021 is a high-severity cross-site scripting (XSS) vulnerability in com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer (maven), affecting versions = 20240325.1. It is fixed in 20260101.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

Is there a fix for CVE-2025-66021?

Yes. CVE-2025-66021 is fixed in 20260101.1. Upgrade to this version or later.

Is CVE-2025-66021 exploitable, and should I be worried?

Whether CVE-2025-66021 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-66021 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-66021

Summary

OWASP Java HTML Sanitizer is vulnerable to XSS via noscript tag and improper style tag sanitization

Impact

This potentially could leads to XSS in applications.
Ref : https://owasp.org/www-community/attacks/xss/

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Affected versions

com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer (= 20240325.1)

Security releases

com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer → 20260101.1 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer to 20260101.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-66021? CVE-2025-66021 is a high-severity cross-site scripting (XSS) vulnerability in com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer (maven), affecting versions = 20240325.1. It is fixed in 20260101.1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
Which versions of com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer are affected by CVE-2025-66021? com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer (maven) versions = 20240325.1 is affected.
Is there a fix for CVE-2025-66021? Yes. CVE-2025-66021 is fixed in 20260101.1. Upgrade to this version or later.
Is CVE-2025-66021 exploitable, and should I be worried? Whether CVE-2025-66021 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-66021 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-66021? Upgrade com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer to 20260101.1 or later.

Other vulnerabilities in com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer

CVE-IDSeverityPackage summary

CVE-2011-4457Lowcom.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer: OWASP HTML Sanitizer allows redirecting to an arbitrary URL when JavaScript is disabled CVE-2021-42575Criticalcom.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer: Policies not properly enforced in OWASP Java HTML Sanitizer