VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.jboss.resteasy:resteasy-client: vulnerability history, versions and safety

org.jboss.resteasy:resteasy-client is a package in the Maven ecosystem. Vulert records 7 vulnerabilities for it across 17 releases, from Jun 2021 to 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
7 vulnerabilities recorded H2 M5
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 org.jboss.resteasy:resteasy-client vulnerabilities

Vulert verdict on org.jboss.resteasy:resteasy-client 7.0.5.Final i

Updated on 23 Oct 2026

Good news: 7.0.5.Final, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 7.

Package health score 76/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

What to do: Stay on 7.0.5.Final or newer. This can change: a vulnerability disclosed tomorrow can affect 7.0.5.Final too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 7.0.5.Final — unaffected i
  • Vulnerabilities on record 7 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 49 packages i
  • Stars 1,144 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month ago i
  • Licence Apache-2.0 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.jboss.resteasy:resteasy-client, 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
7.0.5.Final 18 Sep 2026 none Apache-2.0 — Details →
6.2.19.Final 18 Sep 2026 none Apache-2.0 — Details →
7.0.4.Final 01 Sep 2026 none Apache-2.0 — Details →
6.2.18.Final 01 Sep 2026 none Apache-2.0 — Details →
7.0.3.Final 04 Aug 2026 none Apache-2.0 — Details →
6.2.17.Final 04 Aug 2026 none Apache-2.0 — Details →
7.0.2.Final 15 Apr 2026 none Apache-2.0 — Details →
6.2.16.Final 15 Apr 2026 none Apache-2.0 — Details →
6.2.15.Final 10 Dec 2025 none Apache-2.0 — Details →
7.0.1.Final 10 Dec 2025 none Apache-2.0 — Details →
6.2.14.Final 28 Sep 2025 none Apache-2.0 — Details →
6.2.14.Beta1 27 Sep 2025 none Apache-2.0 — Details →
7.0.0.Final 27 Sep 2025 none Apache-2.0 — Details →
7.0.0.Beta5 27 Sep 2025 none Apache-2.0 — Details →
7.0.0.Beta1 10 Mar 2025 none Apache-2.0 — Details →
6.2.12.Final 10 Mar 2025 none Apache-2.0 — Details →
5.0.10.Final 08 Mar 2025 none Apache-2.0 — Details →
4.7.10.Final 07 Mar 2025 none Apache-2.0 — Details →
7.0.0.Alpha4 11 Nov 2024 none Apache-2.0 — Details →
6.2.11.Final 11 Nov 2024 none Apache-2.0 — Details →
7.0.0.Alpha3 19 Aug 2024 none Apache-2.0 — Details →
6.2.10.Final 19 Aug 2024 none Apache-2.0 — Details →
7.0.0.Alpha2 21 May 2024 none Apache-2.0 — Details →
6.2.9.Final 20 May 2024 none Apache-2.0 — Details →
7.0.0.Alpha1 02 Apr 2024 none Apache-2.0 — Details →
6.2.8.Final 22 Mar 2024 none Apache-2.0 — Details →
6.2.7.Final 12 Jan 2024 none Apache-2.0 — Details →
5.0.9.Final 02 Nov 2023 none Apache-2.0 — Details →
6.2.6.Final 02 Nov 2023 none Apache-2.0 — Details →
6.2.5.Final 22 Aug 2023 none Apache-2.0 — Details →
5.0.8.Final 22 Aug 2023 none Apache-2.0 — Details →
5.0.7.Final 16 May 2023 none Apache-2.0 — Details →
6.2.4.Final 16 May 2023 none Apache-2.0 — Details →
6.2.3.Final 01 Mar 2023 none Apache-2.0 — Details →
5.0.6.Final 01 Mar 2023 none Apache-2.0 — Details →
4.7.9.Final 01 Mar 2023 none Apache-2.0 — Details →
3.15.6.Final 28 Feb 2023 none Apache-2.0 — Details →
4.7.8.Final 03 Feb 2023 none Apache-2.0 — Details →
6.2.2.Final 13 Dec 2022 none Apache-2.0 — Details →
5.0.5.Final 13 Dec 2022 none Apache-2.0 — Details →
6.2.1.Final 10 Oct 2022 none Apache-2.0 — Details →
6.2.0.Final 23 Sep 2022 none Apache-2.0 — Details →
6.2.0.Beta1 08 Sep 2022 none Apache-2.0 — Details →
6.1.0.Final 02 Aug 2022 none Apache-2.0 — Details →
6.1.0.Beta3 21 Jul 2022 none Apache-2.0 — Details →
6.0.3.Final 21 Jul 2022 none Apache-2.0 — Details →
6.0.2.Final 21 Jul 2022 none Apache-2.0 — Details →
5.0.4.Final 21 Jul 2022 none Apache-2.0 — Details →
4.7.7.Final 21 Jul 2022 none Apache-2.0 — Details →
6.1.0.Beta2 27 Apr 2022 none Apache-2.0 — Details →
6.1.0.Beta1 19 Apr 2022 none Apache-2.0 — Details →
6.0.1.Final 19 Apr 2022 none Apache-2.0 — Details →
5.0.3.Final 19 Apr 2022 none Apache-2.0 — Details →
4.7.6.Final 19 Apr 2022 none Apache-2.0 — Details →
6.1.0.Alpha1 31 Mar 2022 none Apache-2.0 — Details →
6.0.0.Final 14 Jan 2022 none Apache-2.0 — Details →
5.0.2.Final 13 Jan 2022 none Apache-2.0 — Details →
4.7.5.Final 13 Jan 2022 none Apache-2.0 — Details →
6.0.0.Beta1 03 Dec 2021 none Apache-2.0 — Details →
5.0.1.Final 03 Dec 2021 none Apache-2.0 — Details →
4.7.4.Final 03 Dec 2021 none Apache-2.0 — Details →
3.15.3.Final 30 Nov 2021 none Apache-2.0 — Details →
5.0.0.Final 04 Nov 2021 none Apache-2.0 — Details →
4.7.3.Final 03 Nov 2021 none Apache-2.0 — Details →
5.0.0.Beta3 28 Oct 2021 none Apache-2.0 — Details →
5.0.0.Beta2 15 Oct 2021 none Apache-2.0 — Details →
5.0.0.Beta1 01 Oct 2021 none Apache-2.0 — Details →
3.11.5.Final 28 Sep 2021 none Apache-2.0 — Details →
4.7.2.Final 23 Sep 2021 none Apache-2.0 — Details →
3.15.2.Final 23 Sep 2021 none Apache-2.0 — Details →
5.0.0.Alpha1 27 Aug 2021 none Apache-2.0 — Details →
4.7.1.Final 24 Jul 2021 none Apache-2.0 — Details →
4.7.0.Final 08 Jul 2021 none Apache-2.0 — Details →
4.7.0.Beta7 07 Jul 2021 none Apache-2.0 — Details →
4.7.0.Beta6 07 Jul 2021 none Apache-2.0 — Details →
4.6.2.Final 05 Jul 2021 none Apache-2.0 — Details →
4.7.0.Beta3 29 Jun 2021 none Apache-2.0 — Details →
4.7.0.Beta2 26 Jun 2021 none Apache-2.0 — Details →
4.7.0.Beta1 23 Jun 2021 none Apache-2.0 — Details →
4.6.1.Final 19 Jun 2021 none Apache-2.0 — Details →
4.6.1.Beta9 18 Jun 2021 none Apache-2.0 — Details →
4.6.1.Beta8 16 Jun 2021 none Apache-2.0 — Details →
4.6.1.Beta7 16 Jun 2021 none Apache-2.0 — Details →
4.6.1.Beta6 16 Jun 2021 none Apache-2.0 — Details →
4.6.1.Beta5 12 Jun 2021 none Apache-2.0 — Details →
4.6.1.Beta3 11 Jun 2021 none Apache-2.0 — Details →
4.6.1.Beta2 27 May 2021 none Apache-2.0 — Details →
4.6.1.Alpha1 25 May 2021 none Apache-2.0 — Details →
4.6.1.Beta1 12 May 2021 none Apache-2.0 — Details →
4.5.12.Final 10 May 2021 H1 Apache-2.0 Yes Details →
4.5.12.Beta1 07 May 2021 H1 Apache-2.0 Yes Details →
4.5.11.Final 21 Apr 2021 H1 Apache-2.0 Yes Details →
4.5.10.Final 15 Apr 2021 H1 Apache-2.0 Yes Details →
3.11.4.Final 23 Mar 2021 none Apache-2.0 — Details →
4.4.3.Final 06 Mar 2021 H1 M1 Apache-2.0 Yes Details →
3.15.1.Final 04 Mar 2021 none Apache-2.0 — Details →
3.15.0.Final 18 Feb 2021 none Apache-2.0 — Details →
4.5.9.Final 06 Feb 2021 H1 Apache-2.0 Yes Details →
4.6.0.Final 13 Jan 2021 H1 Apache-2.0 Yes Details →
4.5.8.SP1 07 Jan 2021 H1 Apache-2.0 Yes Details →
3.15.0.Alpha1 21 Dec 2020 none — — Details →
3.14.0.Final 09 Dec 2020 none — — Details →
3.11.3.Final 02 Dec 2020 none — — Details →
3.13.2.Final 30 Sep 2020 none — — Details →
4.5.8.Final 22 Sep 2020 H1 — Yes Details →
4.5.7.Final 19 Sep 2020 H1 — Yes Details →
3.13.1.Final 13 Sep 2020 none — — Details →
4.5.6.Final 20 Jul 2020 H1 M1 — Yes Details →
3.13.0.Final 18 Jul 2020 none — — Details →
4.5.5.Final 16 Jun 2020 H1 M1 — Yes Details →
4.5.4.Final 11 Jun 2020 H1 M1 — Yes Details →
3.12.1.Final 01 Jun 2020 none — — Details →
3.12.0.Final 17 May 2020 none — — Details →
3.11.2.Final 02 Apr 2020 none — — Details →
4.5.3.Final 26 Mar 2020 H1 M1 — Yes Details →
3.11.1.Final 24 Mar 2020 none — — Details →
4.5.2.Final 04 Mar 2020 H1 M1 — Yes Details →
3.6.1.SP8 02 Mar 2020 none — — Details →
4.5.1.Final 26 Feb 2020 H1 M1 — Yes Details →
4.5.0.Final 22 Feb 2020 H1 M1 — Yes Details →

The newest 120 of 215 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 6

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

03 Vulnerabilities

Recorded vulnerabilities for org.jboss.resteasy:resteasy-client

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-1695: Improper Input Validation in RESTEasy 7.5 high 4.6.0 24 May 2022
CVE-2016-6345: Exposure of Sensitive Information to an Unauthorized Actor in RESTEasy 6.5 medium 3.0.20.Final 17 May 2022
CVE-2016-6347: Cross-Site Scripting Vulnerability in RESTEasy 6.1 medium 3.0.20.Final 17 May 2022
CVE-2016-6348: JacksonJsonpInterceptor susceptible to cross-site script inclusion (XSSI) attack in org.jboss.resteasy:resteasy-client 6.1 medium 3.0.20.Final 17 May 2022
CVE-2020-25633: Generation of Error Message Containing Sensitive Information in RESTEasy client 5.3 medium 4.5.7.Final 03 Jun 2021

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.jboss.resteasy:resteasy-client

Is org.jboss.resteasy:resteasy-client safe to use?

Vulert records 7 vulnerabilities for org.jboss.resteasy:resteasy-client in Maven: 0 critical, 2 high, 5 medium and 0 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 org.jboss.resteasy:resteasy-client's Vulert package health score?

Vulert scores org.jboss.resteasy:resteasy-client 76/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 org.jboss.resteasy:resteasy-client affected?

No. 7.0.5.Final, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of org.jboss.resteasy:resteasy-client should I use?

7.0.5.Final 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.jboss.resteasy:resteasy-client have?

7 vulnerabilities are recorded for org.jboss.resteasy:resteasy-client in the Maven ecosystem: 0 critical, 2 high, 5 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.jboss.resteasy:resteasy-client vulnerabilities disclosed?

0 vulnerabilities were recorded for org.jboss.resteasy:resteasy-client in the last 12 months, and the oldest entry in this database dates to 03 Jun 2021. 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.jboss.resteasy:resteasy-client 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.jboss.resteasy:resteasy-client for upcoming vulnerabilities?

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