VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.owasp.antisamy:antisamy: vulnerability history, versions and safety

org.owasp.antisamy:antisamy is a package in the Maven ecosystem. Vulert records 8 vulnerabilities for it across 36 releases, from Oct 2018 to Feb 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded M8
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.owasp.antisamy:antisamy vulnerabilities

Vulert verdict on org.owasp.antisamy:antisamy 1.7.8 i

Updated on 23 Oct 2026

Careful: 1.7.8 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.7.8 — affected i
  • Vulnerabilities on record 8 over 5 years · 0 in the last year i
  • Latest disclosure 02 Feb 2024 i
  • Highest CVSS 6.1 i
  • With no published fix 1 i
  • Depended on by 396 packages i
  • Last release 17 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.owasp.antisamy:antisamy, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.7.8 07 May 2025 M1 non-standard No Details →
1.7.7 21 Nov 2024 M1 non-standard No Details →
1.7.6 06 Jul 2024 M1 non-standard No Details →
1.7.5 02 Feb 2024 M1 non-standard No Details →
1.7.4 06 Oct 2023 M1 non-standard Yes Details →
1.7.3 12 Apr 2023 M2 non-standard Yes Details →
1.7.2 18 Nov 2022 M2 non-standard Yes Details →
1.7.1 06 Sep 2022 M2 non-standard Yes Details →
1.7.0 16 Jul 2022 M2 non-standard Yes Details →
1.6.8 24 Apr 2022 M2 non-standard Yes Details →
1.6.7 10 Apr 2022 M2 non-standard Yes Details →
1.6.6.1 07 Apr 2022 M3 non-standard Yes Details →
1.6.6 02 Apr 2022 M3 non-standard Yes Details →
1.6.5 01 Feb 2022 M4 non-standard Yes Details →
1.6.4 03 Jul 2021 M4 non-standard Yes Details →
1.6.3 08 Apr 2021 M5 non-standard Yes Details →
1.6.2 18 Mar 2021 M5 non-standard Yes Details →
1.6.1 09 Mar 2021 M5 non-standard Yes Details →
1.6.0 05 Mar 2021 M5 non-standard Yes Details →
1.5.13 13 Jan 2021 M5 non-standard Yes Details →
1.5.12 09 Jan 2021 M5 non-standard Yes Details →
1.5.11 24 Nov 2020 M5 non-standard Yes Details →
1.5.10 24 Jun 2020 M5 non-standard Yes Details →
1.5.9 09 Mar 2020 M5 non-standard Yes Details →
1.5.8 02 Apr 2019 M5 non-standard Yes Details →
1.5.7 28 Sep 2017 M6 non-standard No Details →
1.5.6 27 Jul 2017 M6 non-standard No Details →
1.5.5 22 Dec 2016 M6 non-standard No Details →
1.5.3 27 Jul 2013 M7 non-standard No Details →
1.5.2 24 Apr 2013 M7 non-standard No Details →
1.5.1 14 Feb 2013 M7 non-standard No Details →
1.5 28 Jan 2013 M7 non-standard No Details →
1.4.5 03 Oct 2011 M7 non-standard No Details →
1.4.4 06 Mar 2011 M7 non-standard No Details →
1.4.3 14 Jan 2011 M7 non-standard No Details →
1.4.2 08 Dec 2010 M7 — No Details →

All 36 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 3
  • 2021 1
  • 2022 2
  • 2023 1
  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 8 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.owasp.antisamy:antisamy

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-28367: Cross-site Scripting in OWASP AntiSamy 6.1 medium 1.6.6 23 Apr 2022
CVE-2016-10006: org.owasp.antisamy:antisamy - XSS Vulnerability 6.1 medium 1.5.5 18 Oct 2018
CVE-2021-35043: Cross-site Scripting in OWASP AntiSamy 6.1 medium 1.6.4 02 Aug 2021
CVE-2017-14735: OWASP AntiSamy Cross-site Scripting vulnerability in org.owasp.antisamy:antisamy 6.1 medium 1.5.7 18 Oct 2018
CVE-2022-29577: Cross-site Scripting in OWASP AntiSamy 6.1 medium 1.6.7 23 Apr 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.owasp.antisamy:antisamy

Is org.owasp.antisamy:antisamy safe to use?

Vulert records 8 vulnerabilities for org.owasp.antisamy:antisamy in Maven: 0 critical, 0 high, 8 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is org.owasp.antisamy:antisamy's Vulert package health score?

Vulert scores org.owasp.antisamy:antisamy 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of org.owasp.antisamy:antisamy affected?

Yes. 1.7.8, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of org.owasp.antisamy:antisamy should I use?

1.7.8 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.owasp.antisamy:antisamy have?

8 vulnerabilities are recorded for org.owasp.antisamy:antisamy in the Maven ecosystem: 0 critical, 0 high, 8 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.owasp.antisamy:antisamy vulnerabilities disclosed?

0 vulnerabilities were recorded for org.owasp.antisamy:antisamy in the last 12 months, and the oldest entry in this database dates to 18 Oct 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.owasp.antisamy:antisamy are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.owasp.antisamy:antisamy for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.owasp.antisamy:antisamy version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.