VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

struts:struts: vulnerability history, versions and safety

struts:struts is a package in the Maven ecosystem. Vulert records 4 vulnerabilities for it across 12 releases, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H2 M1 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

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 struts:struts vulnerabilities

Vulert verdict on struts:struts 1.2.9 i

Updated on 22 Oct 2026

Action needed: 1.2.9 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

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

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 1.2.9 — affected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 01 May 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 102 packages i
  • Last release 247 months ago 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 struts:struts, 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.2.9 23 Mar 2006 M1 — Yes Details →
1.2.8 20 Dec 2005 H2 M1 L1 — Yes Details →
1.2.7 22 Nov 2005 H2 M1 L1 Apache-2.0 Yes Details →
1.2.2 22 Nov 2005 H2 M1 L1 — Yes Details →
1.2.4 22 Nov 2005 H2 M1 L1 — Yes Details →
1.1 22 Nov 2005 H2 M1 L1 — Yes Details →
1.1-rc2 22 Nov 2005 H2 M1 L1 — Yes Details →
1.1-b3 22 Nov 2005 H2 M1 L1 — Yes Details →
1.1-beta-2 22 Nov 2005 H2 M1 L1 — Yes Details →
1.1-rc1 22 Nov 2005 H2 M1 L1 — Yes Details →
1.0.2 22 Nov 2005 H2 M1 L1 — Yes Details →
1.1-b2-20021124 01 Aug 2005 H2 M1 L1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 4

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

03 Vulnerabilities

Recorded vulnerabilities for struts:struts

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2006-1547: Improper Input Validation in Apache Struts 7.5 high 1.2.9 01 May 2022
CVE-2006-1546: Apache Struts Improper Input Validation 7.3 high 1.2.9 01 May 2022
CVE-2006-1548: Cross-site scripting in Apache Struts 3.7 low 1.2.9 01 May 2022
CVE-2008-2025: Apache Struts Cross-site Scripting vulnerability N/A medium 1.2.9-162.31.1 01 May 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: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 struts:struts

Is struts:struts safe to use?

Vulert records 4 vulnerabilities for struts:struts in Maven: 0 critical, 2 high, 1 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is struts:struts's Vulert package health score?

Vulert scores struts:struts 74/100, which reads as in good shape. 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).

Is the latest version of struts:struts affected?

Yes. 1.2.9, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of struts:struts should I use?

1.2.9 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 struts:struts have?

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

How often are new struts:struts vulnerabilities disclosed?

0 vulnerabilities were recorded for struts:struts in the last 12 months, and the oldest entry in this database dates to 01 May 2022. 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 struts:struts 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 struts:struts for upcoming vulnerabilities?

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