Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of org.owasp.esapi:esapi before 2.6.0.0 have a Validator.isValidSafeHTML method that can return true for input that is not actually safe, so using that input as-is can in some cases lead to cross-site scripting. The source gives few details on the exact conditions an attacker needs. Upgrade to esapi 2.6.0.0 or later, where the method has been removed. Until then, stop using isValidSafeHTML; Validator.getValidSafeHTML is believed to be safe with the default antisamy-esapi.xml policy.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
No source has published a CVSS score for this record yet.
- CISA KEV Not listed.
- EPSS No score.
Timeline
- 31 Oct 2026, 15:13 UTC First seen by agentprime
- 31 Oct 2026, 15:13 UTC Confirmed by OSV