NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

Cross-site Scripting in OWASP AntiSamyGHSA-9c8w-jrw3-q2c3

MEDIUMFix: nahsra/antisamy#87

GHSA-9c8w-jrw3-q2c3 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.owasp.antisamy:antisamy. A fix is available for org.owasp.antisamy:antisamy — see the affected versions and patch details below.

Also known asCVE-2021-35043
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk
0.00%0.67%1.34%2.01%0.5%1.5%May 26Aug 26Nov 26

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

1 pkg affected
☕org.owasp.antisamy:antisamy

Real-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

OWASP AntiSamy before 1.6.4 allows XSS via HTML attributes when using the HTML output serializer (XHTML is not affected). This was demonstrated by a javascript: URL with &#00058 as the replacement for the : character.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.owasp.antisamy:antisamy≥ 1.5.7&&< 1.6.41.6.4org.owasp.antisamy:antisamy:1.6.4

Affected Products

11 products · 28 configurations
Application
antisamyantisamy_project
< 1.6.4
range
Application
active iq unified managernetapp
all
Application
banking enterprise default managementoracle
5 versions
2.6.22.7.02.7.12.10.02.12.0
Application
banking enterprise default managmentoracle
≥ 2.3.0 && ≤ 2.4.0
range
Application
banking party managementoracle
1 version
2.7.0
Application
banking platformoracle
≥ 2.3.0 && ≤ 2.4.1
3 versions
2.6.22.7.02.7.1

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.owasp.antisamy:antisamy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.owasp.antisamy:antisamy to 1.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9c8w-jrw3-q2c3 is resolved across your whole dependency graph.

  3. Workarounds

    Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

OWASP AntiSamy before 1.6.4 allows XSS via HTML attributes when using the HTML output serializer (XHTML is not affected). This was demonstrated by a javascript: URL with &#00058 as the replacement for the : character.
O3 Security · Impact-Aware SCA

Is GHSA-9c8w-jrw3-q2c3 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Cross-site Scripting in OWASP AntiSamy (Medium 6.1)