# Validator.isValidSafeHTML is being deprecated and will be deleted from org.owasp.esapi:esapi in 1 year

Advisory record · `GHSA-r68h-jhhj-9jvm`

- **Identifiers:** `GHSA-r68h-jhhj-9jvm`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Published:** 27 Nov 2023
- **Updated:** 26 Nov 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 27 Nov 2023, 17:25 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.owasp.esapi:esapi` (Maven): affected `<2.6.0.0`; fixed in `2.6.0.0`

## 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.

Written 8 Nov 2026.

## 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](https://osv.dev/vulnerability/GHSA-r68h-jhhj-9jvm)

## Sources

- [GitHub Advisory Database: GHSA-r68h-jhhj-9jvm](https://github.com/advisories/GHSA-r68h-jhhj-9jvm)
- [OSV: GHSA-r68h-jhhj-9jvm](https://osv.dev/vulnerability/GHSA-r68h-jhhj-9jvm)
- <https://github.com/ESAPI/esapi-java-legacy/security/advisories/GHSA-r68h-jhhj-9jvm>
- <https://github.com/ESAPI/esapi-java-legacy>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-r68h-jhhj-9jvm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-r68h-jhhj-9jvm/>. Everything for agents: <https://agentprime.io/llms.txt>.