VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.httpcomponents.core5:httpcore5: vulnerability history, versions and safety

org.apache.httpcomponents.core5:httpcore5 is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 53 releases, first recorded in Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 01 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.apache.httpcomponents.core5:httpcore5 vulnerabilities

Vulert verdict on org.apache.httpcomponents.core5:httpcore5 5.5-beta4 i

Updated on 23 Oct 2026

Good news: 5.5-beta4, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 5.5-beta4 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 01 Jul 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 4 packages i
  • Last release this month 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.apache.httpcomponents.core5:httpcore5, 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
5.5-beta4 10 Oct 2026 none Apache-2.0 — Details →
5.5-beta3 20 Sep 2026 none Apache-2.0 — Details →
5.4.4 20 Sep 2026 none Apache-2.0 — Details →
5.5-beta2 21 Jun 2026 none Apache-2.0 — Details →
5.4.3 21 Jun 2026 none Apache-2.0 — Details →
5.5-beta1 02 Jun 2026 none Apache-2.0 — Details →
5.5-alpha1 16 Mar 2026 none Apache-2.0 — Details →
5.4.2 01 Mar 2026 H1 Apache-2.0 Yes Details →
5.4.1 07 Feb 2026 H1 Apache-2.0 Yes Details →
5.4 11 Dec 2025 H1 Apache-2.0 Yes Details →
5.4-alpha1 05 Oct 2025 H1 Apache-2.0 Yes Details →
5.3.6 17 Sep 2025 H1 Apache-2.0 Yes Details →
5.3.5 26 Aug 2025 H1 Apache-2.0 Yes Details →
5.3.4 16 Mar 2025 H1 Apache-2.0 Yes Details →
5.3.3 24 Jan 2025 H1 Apache-2.0 Yes Details →
5.3.2 06 Jan 2025 H1 Apache-2.0 Yes Details →
5.3.1 19 Oct 2024 H1 Apache-2.0 Yes Details →
5.3 09 Sep 2024 H1 Apache-2.0 Yes Details →
5.2.5 27 Jun 2024 H1 Apache-2.0 Yes Details →
5.3-beta1 17 Jun 2024 H1 Apache-2.0 Yes Details →
5.3-alpha2 10 Feb 2024 H1 Apache-2.0 Yes Details →
5.3-alpha1 20 Dec 2023 H1 Apache-2.0 Yes Details →
5.2.4 24 Nov 2023 H1 Apache-2.0 Yes Details →
5.2.3 17 Sep 2023 H1 Apache-2.0 Yes Details →
5.2.2 16 Jun 2023 H1 Apache-2.0 Yes Details →
5.2.1 07 Jan 2023 H1 Apache-2.0 Yes Details →
5.1.5 09 Nov 2022 H1 Apache-2.0 Yes Details →
5.2 03 Nov 2022 H1 Apache-2.0 Yes Details →
5.1.4 02 Jul 2022 H1 Apache-2.0 Yes Details →
5.2-beta2 28 May 2022 H1 Apache-2.0 Yes Details →
5.2-beta1 13 Mar 2022 H1 Apache-2.0 Yes Details →
5.1.3 19 Dec 2021 H1 Apache-2.0 Yes Details →
5.2-alpha2 17 Oct 2021 H1 Apache-2.0 Yes Details →
5.1.2 26 Sep 2021 H1 Apache-2.0 Yes Details →
5.2-alpha1 06 Sep 2021 H1 Apache-2.0 Yes Details →
5.1.1 02 May 2021 H1 Apache-2.0 Yes Details →
5.0.4 02 May 2021 H1 Apache-2.0 Yes Details →
5.1 08 Mar 2021 H1 Apache-2.0 Yes Details →
5.1-beta3 01 Feb 2021 H1 Apache-2.0 Yes Details →
5.1-beta2 28 Nov 2020 H1 Apache-2.0 Yes Details →
5.0.3 28 Nov 2020 H1 Apache-2.0 Yes Details →
5.1-beta1 15 Sep 2020 H1 Apache-2.0 Yes Details →
5.0.2 09 Sep 2020 H1 Apache-2.0 Yes Details →
5.0.1 05 Jun 2020 H1 Apache-2.0 Yes Details →
5.0 12 Feb 2020 H1 Apache-2.0 Yes Details →
5.0-beta11 04 Jan 2020 H1 Apache-2.0 Yes Details →
5.0-beta10 28 Oct 2019 H1 Apache-2.0 Yes Details →
5.0-beta9 01 Oct 2019 H1 Apache-2.0 Yes Details →
5.0-beta8 11 Jul 2019 H1 Apache-2.0 Yes Details →
5.0-beta7 27 Feb 2019 H1 Apache-2.0 Yes Details →
5.0-beta6 01 Dec 2018 H1 Apache-2.0 Yes Details →
5.0-beta5 18 Oct 2018 H1 Apache-2.0 Yes Details →
5.0-beta4 15 Oct 2018 H1 Apache-2.0 Yes Details →
5.0-beta3 26 Aug 2018 H1 Apache-2.0 Yes Details →
5.0-beta2 11 Jan 2018 H1 Apache-2.0 Yes Details →
5.0-beta1 02 Nov 2017 H1 Apache-2.0 Yes Details →
5.0-alpha4 28 Aug 2017 H1 Apache-2.0 Yes Details →
5.0-alpha3 27 Apr 2017 H1 Apache-2.0 Yes Details →
5.0-alpha2 22 Dec 2016 H1 Apache-2.0 Yes Details →
5.0-alpha1 20 Dec 2015 H1 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for org.apache.httpcomponents.core5:httpcore5

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-54399: Apache HttpComponents Core HTTP/1 Header Parsing Memory Exhaustion Vulnerability 7.5 high 5.4.3 01 Jul 2026

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.apache.httpcomponents.core5:httpcore5

Is org.apache.httpcomponents.core5:httpcore5 safe to use?

Vulert records 1 vulnerabilities for org.apache.httpcomponents.core5:httpcore5 in Maven: 0 critical, 1 high, 0 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.apache.httpcomponents.core5:httpcore5's Vulert package health score?

Vulert scores org.apache.httpcomponents.core5:httpcore5 78/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.apache.httpcomponents.core5:httpcore5 affected?

No. 5.5-beta4, 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.apache.httpcomponents.core5:httpcore5 should I use?

5.5-beta4 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.apache.httpcomponents.core5:httpcore5 have?

1 vulnerability is recorded for org.apache.httpcomponents.core5:httpcore5 in the Maven ecosystem: 0 critical, 1 high, 0 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.apache.httpcomponents.core5:httpcore5 vulnerabilities disclosed?

1 vulnerability was recorded for org.apache.httpcomponents.core5:httpcore5 in the last 12 months, and the oldest entry in this database dates to 01 Jul 2026. 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.apache.httpcomponents.core5:httpcore5 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.apache.httpcomponents.core5:httpcore5 for upcoming vulnerabilities?

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