BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-71290High confidence

Apache HttpComponents Client: TLS hostname verification silently disabled on the async transport (default config, MITM)

Apache Software Foundation · Apache HttpComponents Client

9.1CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 12 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.33% for the current model date.

Compensating controls

  • Apply the linked authoritative mitigation while planning the permanent fix.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Apache Software Foundation Apache HttpComponents Client and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 12 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

9 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcehttpcomponents-clientNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian trixietrixie · sourcehttpcomponents-core5Not affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcehttpcomponents-clientNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcehttpcomponents-core5Not affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcehttpcomponents-clientNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcehttpcomponents-core5Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcehttpcomponents-clientNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcehttpcomponents-core5Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivehttpcomponents-core5Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-71290 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityorg.apache.httpcomponents.client5/httpclient5: Apache HttpComponents Client: Server impersonation via improper TLS hostname verification
8 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3
  • httpclient5 as a component of Red Hat build of Apicurio Registry 3
  • quarkus-apache-httpclient as a component of Red Hat build of Apicurio Registry 3
  • httpclient5 as a component of Red Hat build of Debezium 3
  • rhoai/odh-modelmesh-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
  • devspaces/jetbrains-ide-rhel9 as a component of Red Hat OpenShift Dev Spaces
  • devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces
  • devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces
Summary
A flaw was found in the asynchronous version of Apache HttpComponents Client. This improper Transport Layer Security (TLS) hostname verification vulnerability allows a remote attacker to intercept and modify network traffic. By presenting a valid certificate for a different domain, an attacker can impersonate the server, leading to a Man-in-the-Middle (MITM) attack and compromising communication.
Remediation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-56973

No EUVD known-exploited evidence

Improper TLS hostname verification vulnerability in Apache HttpComponents Client 5.4 or newer. HostnameVerificationPolicy#BUILTIN setting has no effect when used with the async version of HttpClient. An attacker that can intercept and modify traffic between the client and the server can impersonate the server by presenting a valid certificate for a different domain.  Please note the classic version of HttpClient is not affected by this vulnerability.  Affected users are recommended to upgrade to at least version 5.6.4, which fixes the issue.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
9.1 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 12 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Improper TLS hostname verification vulnerability in Apache HttpComponents Client 5.4 or newer. HostnameVerificationPolicy#BUILTIN setting has no effect when used with the async version of HttpClient. An attacker that can intercept and modify traffic between the client and the server can impersonate the server by presenting a valid certificate for a different domain.  Please note the classic version of HttpClient is not affected by this vulnerability.  Affected users are recommended to upgrade to at least version 5.6.4, which fixes the issue.

What

Improper TLS hostname verification vulnerability in Apache HttpComponents Client 5.4 or newer. HostnameVerificationPolicy#BUILTIN setting has no effect when used with the async version of HttpClient. An attacker that can intercept and modify traffic between the client and the server can impersonate the server by presenting a valid certificate for a different domain.  Please note the classic version of HttpClient is not affected by this vulnerability.  Affected users are recommended to upgrade to at least version 5.6.4, which fixes the issue.

Why

The product does not validate, or incorrectly validates, a certificate.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Improper TLS hostname verification vulnerability in Apache HttpComponents Client 5.4 or newer. HostnameVerificationPolicy#BUILTIN setting has no effect when used with the async version of HttpClient. An attacker that can intercept and modify traffic between the client and the server can impersonate the server by presenting a valid certificate for a different domain.  Please note the classic version of HttpClient is not affected by this vulnerability.  Affected users are recommended to upgrade to at least version 5.6.4, which fixes the issue.

Why

The product does not validate, or incorrectly validates, a certificate.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Certificate Validation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-295 ↗

CWE-295: Improper Certificate Validation. The product does not validate, or incorrectly validates, a certificate.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-295
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-56973Official EUVD mapping

Improper TLS hostname verification vulnerability in Apache HttpComponents Client 5.4 or newer. HostnameVerificationPolicy#BUILTIN setting has no effect when used with the async version of HttpClient. An attacker that can intercept and modify traffic between the client and the server can impersonate the server by presenting a valid certificate for a different domain.  Please note the classic version of HttpClient is not affected by this vulnerability.  Affected users are recommended to upgrade to at least version 5.6.4, which fixes the issue.

Official EUVD record ↗
BSI · German · WID-SEC-2026-3403Oracle Communications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Communications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-2782Apache HttpComponents: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Apache HttpComponents ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1233Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-66010 Référence CVE CVE-2026-67213 https://www.cve.org/CVERecord?id=CVE-2026-67213 Référence CVE CVE-2026-67214 https://www.cve.org/CVERecord?id=CVE-2026-67214 Référence CVE CVE-2026-69152 https://www.cve.org/CVERecord?id=CVE-2026-69152 Référence CVE CVE-2026-69153 https://www.cve.org/CVERecord?id=CVE-2026-69153 Référence CVE CVE-2026-69247 https://www.cve.org/CVERecord?id=CVE-2026-69247 Référence CVE CVE-2026-69248 https://www.cve.org/CVERecord?id=CVE-2026-69248 Référence CVE CVE-2026-69249 https://www.cve.org/CVERecord?id=CVE-2026-69249 Référence CVE CVE-2026-70907 https://www.cve.org/CVERecord?id=CVE-2026-70907 Référence CVE CVE-2026-71290 https://www.cve.org/CVERecord?id=CVE-2026-71290 Référence CVE CVE-2026-7168 https://www.cve.org/CVERecord?id=CVE-2026-7168 Référence CVE CVE-2026-71852 https://www.cve.org/CVERecord?id=CVE-2026-71852 Référence CVE CVE-2026-71870 https://www.cve.org/CVERecord?id=CVE-2026-71870 Référence CVE CVE-2026-72848 https://www.cve.org/CVERecord?id=CVE-2026-72848 Référence CVE CVE-2026-73088 https://www.cve.org/CVERecord?id=CVE-2026-73088 Référence CVE CVE-2026-73089 https://www.cve.org/CVERecord?id=CVE-2026-73089 Référence CVE CVE-2026-73646 https://www.cve.org/CVERecord?id=CVE-2026-73646 Référence CVE CVE-2026-75509 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2026-68569 Référence CVE CVE-2026-68763 https://www.cve.org/CVERecord?id=CVE-2026-68763 Référence CVE CVE-2026-68945 https://www.cve.org/CVERecord?id=CVE-2026-68945 Référence CVE CVE-2026-69151 https://www.cve.org/CVERecord?id=CVE-2026-69151 Référence CVE CVE-2026-69152 https://www.cve.org/CVERecord?id=CVE-2026-69152 Référence CVE CVE-2026-69153 https://www.cve.org/CVERecord?id=CVE-2026-69153 Référence CVE CVE-2026-69247 https://www.cve.org/CVERecord?id=CVE-2026-69247 Référence CVE CVE-2026-6938 https://www.cve.org/CVERecord?id=CVE-2026-6938 Référence CVE CVE-2026-70907 https://www.cve.org/CVERecord?id=CVE-2026-70907 Référence CVE CVE-2026-71290 https://www.cve.org/CVERecord?id=CVE-2026-71290 Référence CVE CVE-2026-71491 https://www.cve.org/CVERecord?id=CVE-2026-71491 Référence CVE CVE-2026-73088 https://www.cve.org/CVERecord?id=CVE-2026-73088 Référence CVE CVE-2026-73089 https://www.cve.org/CVERecord?id=CVE-2026-73089 Référence CVE CVE-2026-73180 https://www.cve.org/CVERecord?id=CVE-2026-73180 Référence CVE CVE-2026-75595 https://www.cve.org/CVERecord?id=CVE-2026-75595 Référence CVE CVE-2026-75596 https://www.cve.org/CVERecord?id=CVE-2026-75596 Référence CVE CVE-2026-75838 https://www.cve.org/CVERecord?id=CVE-2026-75838 Référence CVE CVE-2026-77310 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-028775Apache Software FoundationのHttpClientにおける証明書検証に関する脆弱性

Apache HttpComponents Client 5.4以降におけるTLSホスト名検証の不備による脆弱性です。HostnameVerificationPolicy#BUILTIN設定は、HttpClientの非同期バージョン使用時に効果を発揮しません。攻撃者がクライアントとサーバー間の通信を傍受・改ざんできる場合、異なるドメインの有効な証明書を提示してサーバーをなりすますことが可能です。なお、クラシックバージョンのHttpClientはこの脆弱性の影響を受けません。影響を受けるユーザーには、問題を修正したバージョン5.6.4以降へアップグレードすることを推奨します。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0375Kwetsbaarheden verholpen in Oracle Communications

De kwetsbaarheden betreffen verschillende beveiligingsproblemen in Oracle Communications-producten, waaronder mogelijkheden voor niet-geauthenticeerde en laaggeprivilegieerde kwaadwillenden om via netwerktoegang ongeautoriseerde acties uit te voeren. De kwetsbaarheden hebben CVSS-scores variërend van laag tot kritiek. Van de in totaal 31 kwetsbaarheden zijn vier als kritiek aangemerkt en kunnen 23 kwetsbaarheden zonder authenticatie op afstand worden misbruikt. Succesvol misbruik kan onder meer leiden tot het verkrijgen van ongeautoriseerde toegang tot gevoelige informatie, het wijzigen van gegevens en het verstoren van de beschikbaarheid van getroffen systemen. Sommige kwetsbaarheden vereisen gebruikersinteractie of voorafgaande toegangsrechten, terwijl andere volledig op afstand en zonder authenticatie kunnen worden misbruikt. De vier kwetsbaarheden die als kritiek zijn aangemerkt, CVE-2026-44024, CVE-2026-17544, CVE-2026-71290 en CVE-2026-73194, hebben een CVSS-score van 9,1 of hoger en bevinden zich in verschillende Core-componenten van Oracle Communications Unified Assurance, waaronder Fluentd, PHP, Apache HttpClient en DBI. Deze kwetsbaarheden kunnen zonder authenticatie op afstand worden misbruikt en kunnen een hoge impact hebben op de vertrouwelijkheid en, afhankelijk van de kwetsbaarheid, de integriteit en beschikbaarheid van getroffen systemen. Het NCSC adviseert om de beveiligingsupdates voor de kritieke kwetsbaarheden met voorrang toe te passen.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
04

Evidence and provenance

Published 11 Aug 2026 · Last source change 24 Sept 2026, 03:55 UTC · CWE-295 · Improper Certificate Validation

CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-56973
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    5.4-alpha ≤ 5.6.3 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    Apache HttpComponents Client: 5.4-alpha ≤ 5.6.3 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; httpclient5 as a component of Red Hat build of Apicurio Registry 3; quarkus-apache-httpclient as a component of Red Hat build of Apicurio Registry 3; httpclient5 as a component of Red Hat build of Debezium 3; devspaces/jetbrains-ide-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces
    After
    httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; httpclient5 as a component of Red Hat build of Apicurio Registry 3; quarkus-apache-httpclient as a component of Red Hat build of Apicurio Registry 3; httpclient5 as a component of Red Hat build of Debezium 3; rhoai/odh-modelmesh-rhel9 as a component of Red Hat OpenShift AI (RHOAI); devspaces/jetbrains-ide-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-71290 to remediation: access.redhat.com/CVE-2026-71290.
    Before
    remediation: access.redhat.com/CVE-2026-71290
    After
    remediation: access.redhat.com/CVE-2026-71290
    Red Hat Product Security ↗
  4. Remediation statusRemediation status changed from Patch available to Mitigation available.
    Before
    Patch available
    After
    Mitigation available
    Red Hat Product Security ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    camel-quarkus-support-httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; httpclient5-cache as a component of Red Hat build of Apache Camel 4 for Quarkus 3; quarkus-apache-httpclient as a component of Red Hat build of Apache Camel 4 for Quarkus 3; httpclient5 as a component of Red Hat build of Apicurio Registry 3; quarkus-apache-httpclient as a component of Red Hat build of Apicurio Registry 3; httpclient5 as a component of Red Hat build of Debezium 3; quarkus-apache-httpclient as a component of Red Hat build of Quarkus; devspaces/jetbrains-ide-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces · Fixed: Red Hat Build of Apache Camel 3.33 for Quarkus 3.33.3.SP1
    After
    httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; httpclient5 as a component of Red Hat build of Apicurio Registry 3; quarkus-apache-httpclient as a component of Red Hat build of Apicurio Registry 3; httpclient5 as a component of Red Hat build of Debezium 3; devspaces/jetbrains-ide-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces
    Red Hat Product Security ↗
  6. Affected versionsThe structured affected or fixed version information changed.
    Before
    camel-quarkus-support-httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-quarkus-support-httpclient5-deployment as a component of Red Hat build of Apache Camel 4 for Quarkus 3; httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; httpclient5-cache as a component of Red Hat build of Apache Camel 4 for Quarkus 3; quarkus-apache-httpclient as a component of Red Hat build of Apache Camel 4 for Quarkus 3; httpclient5 as a component of Red Hat build of Apicurio Registry 3; quarkus-apache-httpclient as a component of Red Hat build of Apicurio Registry 3; httpclient5 as a component of Red Hat build of Debezium 3; quarkus-apache-httpclient as a component of Red Hat build of Quarkus; devspaces/jetbrains-ide-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces · Fixed: Red Hat Build of Apache Camel 3.33 for Quarkus 3.33.3.SP1
    After
    camel-quarkus-support-httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; httpclient5-cache as a component of Red Hat build of Apache Camel 4 for Quarkus 3; quarkus-apache-httpclient as a component of Red Hat build of Apache Camel 4 for Quarkus 3; httpclient5 as a component of Red Hat build of Apicurio Registry 3; quarkus-apache-httpclient as a component of Red Hat build of Apicurio Registry 3; httpclient5 as a component of Red Hat build of Debezium 3; quarkus-apache-httpclient as a component of Red Hat build of Quarkus; devspaces/jetbrains-ide-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces · Fixed: Red Hat Build of Apache Camel 3.33 for Quarkus 3.33.3.SP1
    Red Hat Product Security ↗
  7. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-71290 to remediation: access.redhat.com/CVE-2026-71290.
    Before
    remediation: access.redhat.com/CVE-2026-71290
    After
    remediation: access.redhat.com/CVE-2026-71290
    Red Hat Product Security ↗
  8. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  9. Affected versionsThe structured affected or fixed version information changed.
    Before
    camel-quarkus-support-httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-quarkus-support-httpclient5-deployment as a component of Red Hat build of Apache Camel 4 for Quarkus 3; quarkus-apache-httpclient as a component of Red Hat build of Quarkus; devspaces/jetbrains-ide-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces
    After
    camel-quarkus-support-httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-quarkus-support-httpclient5-deployment as a component of Red Hat build of Apache Camel 4 for Quarkus 3; httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; httpclient5-cache as a component of Red Hat build of Apache Camel 4 for Quarkus 3; quarkus-apache-httpclient as a component of Red Hat build of Apache Camel 4 for Quarkus 3; httpclient5 as a component of Red Hat build of Apicurio Registry 3; quarkus-apache-httpclient as a component of Red Hat build of Apicurio Registry 3; httpclient5 as a component of Red Hat build of Debezium 3; quarkus-apache-httpclient as a component of Red Hat build of Quarkus; devspaces/jetbrains-ide-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces · Fixed: Red Hat Build of Apache Camel 3.33 for Quarkus 3.33.3.SP1
    Red Hat Product Security ↗
  10. Affected versionsThe structured affected or fixed version information changed.
    Before
    camel-quarkus-support-httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-quarkus-support-httpclient5-deployment as a component of Red Hat build of Apache Camel 4 for Quarkus 3; devspaces/jetbrains-ide-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces
    After
    camel-quarkus-support-httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-quarkus-support-httpclient5-deployment as a component of Red Hat build of Apache Camel 4 for Quarkus 3; quarkus-apache-httpclient as a component of Red Hat build of Quarkus; devspaces/jetbrains-ide-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces
    Red Hat Product Security ↗
  11. Affected versionsThe structured affected or fixed version information changed.
    Before
    devspaces/jetbrains-ide-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces
    After
    camel-quarkus-support-httpclient5 as a component of Red Hat build of Apache Camel 4 for Quarkus 3; camel-quarkus-support-httpclient5-deployment as a component of Red Hat build of Apache Camel 4 for Quarkus 3; devspaces/jetbrains-ide-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces
    Red Hat Product Security ↗
  12. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-71290 to remediation: access.redhat.com/CVE-2026-71290.
    Before
    remediation: access.redhat.com/CVE-2026-71290
    After
    remediation: access.redhat.com/CVE-2026-71290
    Red Hat Product Security ↗
  13. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Red Hat Product Security ↗
  14. Affected versionsThe structured affected or fixed version information changed.
    Before
    After
    devspaces/jetbrains-ide-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/openvsx-rhel9 as a component of Red Hat OpenShift Dev Spaces; devspaces/pluginregistry-rhel9 as a component of Red Hat OpenShift Dev Spaces
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2026-56973↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-71290 · cve.blacktree.nl