BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2023-26159High confidence

Versions of the package follow-redirects before 1.15.4 are vulnerable to Improper Input Validation due to the improper handling of URLs by the url.parse() function

Unknown · follow-redirects

7.3HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state 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 severityHighOperational priority:Critical, raised one band.upgradedsince 3 Nov 2025

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.80% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown follow-redirects and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  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 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

4 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 1 affected package state 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 · sourcenode-follow-redirectsVendor fix publishedDebian records a fixed source-package version for this release.1.15.6+~1.14.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcenode-follow-redirectsAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcenode-follow-redirectsVendor fix publishedDebian records a fixed source-package version for this release.1.15.6+~1.14.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcenode-follow-redirectsVendor fix publishedDebian records a fixed source-package version for this release.1.15.6+~1.14.4-1Debian Security Tracker ↗Source updated 5 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmfollow-redirects< 1.15.41.15.4GitHub advisory ↗github reviewed aggregator · 4 Nov 2025
npmfollow-redirectsSEMVER: introduced 0; fixed 1.15.41.15.4OSV record ↗aggregator derived · 10 Sep 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-2023-26159 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityfollow-redirects: Improper Input Validation due to the improper handling of URLs by the url.parse()
29 known affected

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

  • follow-redirects.src as a component of Cryostat 2
  • openshift-pipelines/pipelines-hub-api-rhel8 as a component of OpenShift Pipelines
  • openshift-pipelines/pipelines-hub-db-migration-rhel8 as a component of OpenShift Pipelines
  • openshift-pipelines/pipelines-hub-ui-rhel8 as a component of OpenShift Pipelines
  • openshift-service-mesh/kiali-rhel8 as a component of OpenShift Service Mesh 2
  • 3scale-amp-system-container as a component of Red Hat 3scale API Management Platform 2
  • advanced-cluster-security/rhacs-main-rhel8 as a component of Red Hat Advanced Cluster Security 3
  • advanced-cluster-security/rhacs-main-rhel8 as a component of Red Hat Advanced Cluster Security 4
  • follow-redirects.src as a component of Red Hat build of Apicurio Registry 2
  • follow-redirects.src as a component of Red Hat build of OptaPlanner 8
  • follow-redirects.src as a component of Red Hat Data Grid 8
  • follow-redirects.src as a component of Red Hat Decision Manager 7
Summary
An Improper Input Validation flaw was found in follow-redirects due to the improper handling of URLs by the url.parse() function. When a new URL() throws an error, it can be manipulated to misinterpret the hostname. This issue could allow an attacker to redirect traffic to a malicious site, potentially leading to information disclosure, phishing attacks, or other security breaches.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
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-2024-0377

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Versions of the package follow-redirects before 1.15.4 are vulnerable to Improper Input Validation due to the improper handling of URLs by the url.parse() function. When new URL() throws an error, it can be manipulated to misinterpret the hostname. An attacker could exploit this weakness to redirect traffic to a malicious site, potentially leading to information disclosure, phishing attacks, or other security breaches.

What

Versions of the package follow-redirects before 1.15.4 are vulnerable to Improper Input Validation due to the improper handling of URLs by the url.parse() function. When new URL() throws an error, it can be manipulated to misinterpret the hostname. An attacker could exploit this weakness to redirect traffic to a malicious site, potentially leading to information disclosure, phishing attacks, or other security breaches.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

What

Versions of the package follow-redirects before 1.15.4 are vulnerable to Improper Input Validation due to the improper handling of URLs by the url.parse() function. When new URL() throws an error, it can be manipulated to misinterpret the hostname. An attacker could exploit this weakness to redirect traffic to a malicious site, potentially leading to information disclosure, phishing attacks, or other security breaches.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may obtain information outside the intended access boundary.

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.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Improper Input Validation → obtain information outside the intended access boundary
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-20 ↗

CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

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:L/I:L/A:L/E:P

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.CLowConfidentiality impact: A successful attack can cause a limited loss.ILowIntegrity impact: A successful attack can cause a limited loss.ALowAvailability impact: A successful attack can cause a limited loss.
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-20Public exploit reference
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-0180Dell Data Protection Advisor: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell Data Protection Advisor ausnutzen, um beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu erzeugen, Sicherheitsmaßnahmen zu umgehen und nicht näher spezifizierte Angriffe zu starten.

Official advisory ↗
BSI · German · WID-SEC-2024-3344HCL BigFix WebUI: Mehrere Open Source Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in HCL BigFix WebU ausnutzen, um die Vertraulichkeit, Verfügbarkeit und Integrität zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2024-1226Red Hat OpenShift: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um Dateien zu manipulieren, einen Denial-of-Service-Zustand zu verursachen, beliebigen Code auszuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder um weitere nicht spezifizierte Angriffe auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-0858IBM QRadar SIEM: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um Phishing-Angriffe durchzuführen, Sicherheitsmaßnahmen zu umgehen, beliebigen Code auszuführen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
BSI · German · WID-SEC-2024-0521IBM MQ: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM MQ ausnutzen, um beliebigen Programmcode auszuführen, Informationen offenzulegen oder einen Denial of Service Zustand herbeizuführen.

Official advisory ↗
BSI · German · WID-SEC-2025-0010HCL BigFix Server Automation: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in HCL BigFix Server Automation ausnutzen, um Dateien zu manipulieren, vertrauliche Informationen preiszugeben und Phishing-Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-0277IBM Business Automation Workflow: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM Business Automation Workflow ausnutzen, um einen Cross-Site-Scripting-Angriff zu starten, einen Phishing-Angriff durchzuführen, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.

Official advisory ↗
BSI · German · WID-SEC-2024-0168Red Hat OpenShift: Schwachstelle ermöglicht Offenlegung von Informationen

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat OpenShift ausnutzen, um Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240103Security Bulletin 03 Jan 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 03 Jan 2024, published on 3 January 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

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

ord?id=CVE-2023-22067 Référence CVE CVE-2023-22081 https://www.cve.org/CVERecord?id=CVE-2023-22081 Référence CVE CVE-2023-23918 https://www.cve.org/CVERecord?id=CVE-2023-23918 Référence CVE CVE-2023-23919 https://www.cve.org/CVERecord?id=CVE-2023-23919 Référence CVE CVE-2023-23920 https://www.cve.org/CVERecord?id=CVE-2023-23920 Référence CVE CVE-2023-23936 https://www.cve.org/CVERecord?id=CVE-2023-23936 Référence CVE CVE-2023-24807 https://www.cve.org/CVERecord?id=CVE-2023-24807 Référence CVE CVE-2023-24998 https://www.cve.org/CVERecord?id=CVE-2023-24998 Référence CVE CVE-2023-2597 https://www.cve.org/CVERecord?id=CVE-2023-2597 Référence CVE CVE-2023-26159 https://www.cve.org/CVERecord?id=CVE-2023-26159 Référence CVE CVE-2023-33850 https://www.cve.org/CVERecord?id=CVE-2023-33850 Référence CVE CVE-2023-38264 https://www.cve.org/CVERecord?id=CVE-2023-38264 Référence CVE CVE-2023-38737 https://www.cve.org/CVERecord?id=CVE-2023-38737 Référence CVE CVE-2023-39332 https://www.cve.org/CVERecord?id=CVE-2023-39332 Référence CVE CVE-2023-44483 https://www.cve.org/CVERecord?id=CVE-2023-44483 Référence CVE CVE-2023-44487 https://www.cve.org/CVERecord?id=CVE-2023-44487 Référence CVE CVE-2023-49735 https://www.cve.org/CVERecord?id=CVE-2023-49735 Référence CVE CVE-2023-50312 https://www.cve.org/CVERecord?id=

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

7176657 du 20 novembre 2024 https://www.ibm.com/support/pages/node/7176657 Bulletin de sécurité IBM 7176660 du 20 novembre 2024 https://www.ibm.com/support/pages/node/7176660 Référence CVE CVE-2016-10735 https://www.cve.org/CVERecord?id=CVE-2016-10735 Référence CVE CVE-2018-14040 https://www.cve.org/CVERecord?id=CVE-2018-14040 Référence CVE CVE-2018-14041 https://www.cve.org/CVERecord?id=CVE-2018-14041 Référence CVE CVE-2018-20676 https://www.cve.org/CVERecord?id=CVE-2018-20676 Référence CVE CVE-2018-20677 https://www.cve.org/CVERecord?id=CVE-2018-20677 Référence CVE CVE-2019-8331 https://www.cve.org/CVERecord?id=CVE-2019-8331 Référence CVE CVE-2023-26159 https://www.cve.org/CVERecord?id=CVE-2023-26159 Référence CVE CVE-2023-51775 https://www.cve.org/CVERecord?id=CVE-2023-51775 Référence CVE CVE-2024-0760 https://www.cve.org/CVERecord?id=CVE-2024-0760 Référence CVE CVE-2024-1135 https://www.cve.org/CVERecord?id=CVE-2024-1135 Référence CVE CVE-2024-1737 https://www.cve.org/CVERecord?id=CVE-2024-1737 Référence CVE CVE-2024-1975 https://www.cve.org/CVERecord?id=CVE-2024-1975 Référence CVE CVE-2024-22354 https://www.cve.org/CVERecord?id=CVE-2024-22354 Référence CVE CVE-2024-28849 https://www.cve.org/CVERecord?id=CVE-2024-28849 Référence CVE CVE-2024-34064 https://www.cve.org/CVERecord?id=CVE-2024

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0959Multiples vulnérabilités dans les produits NetApp

ecord?id=CVE-2021-23358 Référence CVE CVE-2021-3377 https://www.cve.org/CVERecord?id=CVE-2021-3377 Référence CVE CVE-2021-36770 https://www.cve.org/CVERecord?id=CVE-2021-36770 Référence CVE CVE-2022-24785 https://www.cve.org/CVERecord?id=CVE-2022-24785 Référence CVE CVE-2022-31129 https://www.cve.org/CVERecord?id=CVE-2022-31129 Référence CVE CVE-2022-3715 https://www.cve.org/CVERecord?id=CVE-2022-3715 Référence CVE CVE-2023-22067 https://www.cve.org/CVERecord?id=CVE-2023-22067 Référence CVE CVE-2023-22081 https://www.cve.org/CVERecord?id=CVE-2023-22081 Référence CVE CVE-2023-24998 https://www.cve.org/CVERecord?id=CVE-2023-24998 Référence CVE CVE-2023-26159 https://www.cve.org/CVERecord?id=CVE-2023-26159 Référence CVE CVE-2023-2976 https://www.cve.org/CVERecord?id=CVE-2023-2976 Référence CVE CVE-2023-33850 https://www.cve.org/CVERecord?id=CVE-2023-33850 Référence CVE CVE-2023-37466 https://www.cve.org/CVERecord?id=CVE-2023-37466 Référence CVE CVE-2023-37903 https://www.cve.org/CVERecord?id=CVE-2023-37903 Référence CVE CVE-2023-38552 https://www.cve.org/CVERecord?id=CVE-2023-38552 Référence CVE CVE-2023-39331 https://www.cve.org/CVERecord?id=CVE-2023-39331 Référence CVE CVE-2023-39332 https://www.cve.org/CVERecord?id=CVE-2023-39332 Référence CVE CVE-2023-39333 https://www.cve.org/CVERecord?id=CV

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

ord?id=CVE-2022-24785 Référence CVE CVE-2022-24903 https://www.cve.org/CVERecord?id=CVE-2022-24903 Référence CVE CVE-2022-25647 https://www.cve.org/CVERecord?id=CVE-2022-25647 Référence CVE CVE-2022-29622 https://www.cve.org/CVERecord?id=CVE-2022-29622 Référence CVE CVE-2022-31129 https://www.cve.org/CVERecord?id=CVE-2022-31129 Référence CVE CVE-2022-3715 https://www.cve.org/CVERecord?id=CVE-2022-3715 Référence CVE CVE-2023-22067 https://www.cve.org/CVERecord?id=CVE-2023-22067 Référence CVE CVE-2023-22081 https://www.cve.org/CVERecord?id=CVE-2023-22081 Référence CVE CVE-2023-24998 https://www.cve.org/CVERecord?id=CVE-2023-24998 Référence CVE CVE-2023-26159 https://www.cve.org/CVERecord?id=CVE-2023-26159 Référence CVE CVE-2023-2976 https://www.cve.org/CVERecord?id=CVE-2023-2976 Référence CVE CVE-2023-33850 https://www.cve.org/CVERecord?id=CVE-2023-33850 Référence CVE CVE-2023-37466 https://www.cve.org/CVERecord?id=CVE-2023-37466 Référence CVE CVE-2023-37903 https://www.cve.org/CVERecord?id=CVE-2023-37903 Référence CVE CVE-2023-38552 https://www.cve.org/CVERecord?id=CVE-2023-38552 Référence CVE CVE-2023-39331 https://www.cve.org/CVERecord?id=CVE-2023-39331 Référence CVE CVE-2023-39332 https://www.cve.org/CVERecord?id=CVE-2023-39332 Référence CVE CVE-2023-39333 https://www.cve.org/CVERecord?id=CV

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

rd?id=CVE-2021-4104 Référence CVE CVE-2022-23302 https://www.cve.org/CVERecord?id=CVE-2022-23302 Référence CVE CVE-2022-23305 https://www.cve.org/CVERecord?id=CVE-2022-23305 Référence CVE CVE-2022-23307 https://www.cve.org/CVERecord?id=CVE-2022-23307 Référence CVE CVE-2022-25647 https://www.cve.org/CVERecord?id=CVE-2022-25647 Référence CVE CVE-2022-46751 https://www.cve.org/CVERecord?id=CVE-2022-46751 Référence CVE CVE-2023-22946 https://www.cve.org/CVERecord?id=CVE-2023-22946 Référence CVE CVE-2023-25613 https://www.cve.org/CVERecord?id=CVE-2023-25613 Référence CVE CVE-2023-26145 https://www.cve.org/CVERecord?id=CVE-2023-26145 Référence CVE CVE-2023-26159 https://www.cve.org/CVERecord?id=CVE-2023-26159 Référence CVE CVE-2023-26464 https://www.cve.org/CVERecord?id=CVE-2023-26464 Référence CVE CVE-2023-31486 https://www.cve.org/CVERecord?id=CVE-2023-31486 Référence CVE CVE-2023-31582 https://www.cve.org/CVERecord?id=CVE-2023-31582 Référence CVE CVE-2023-33850 https://www.cve.org/CVERecord?id=CVE-2023-33850 Référence CVE CVE-2023-34453 https://www.cve.org/CVERecord?id=CVE-2023-34453 Référence CVE CVE-2023-34454 https://www.cve.org/CVERecord?id=CVE-2023-34454 Référence CVE CVE-2023-34455 https://www.cve.org/CVERecord?id=CVE-2023-34455 Référence CVE CVE-2023-34462 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-23540 Référence CVE CVE-2022-23541 https://www.cve.org/CVERecord?id=CVE-2022-23541 Référence CVE CVE-2022-29162 https://www.cve.org/CVERecord?id=CVE-2022-29162 Référence CVE CVE-2022-31116 https://www.cve.org/CVERecord?id=CVE-2022-31116 Référence CVE CVE-2022-31117 https://www.cve.org/CVERecord?id=CVE-2022-31117 Référence CVE CVE-2022-40897 https://www.cve.org/CVERecord?id=CVE-2022-40897 Référence CVE CVE-2023-23934 https://www.cve.org/CVERecord?id=CVE-2023-23934 Référence CVE CVE-2023-25577 https://www.cve.org/CVERecord?id=CVE-2023-25577 Référence CVE CVE-2023-25809 https://www.cve.org/CVERecord?id=CVE-2023-25809 Référence CVE CVE-2023-26159 https://www.cve.org/CVERecord?id=CVE-2023-26159 Référence CVE CVE-2023-27561 https://www.cve.org/CVERecord?id=CVE-2023-27561 Référence CVE CVE-2023-28642 https://www.cve.org/CVERecord?id=CVE-2023-28642 Référence CVE CVE-2023-28840 https://www.cve.org/CVERecord?id=CVE-2023-28840 Référence CVE CVE-2023-28841 https://www.cve.org/CVERecord?id=CVE-2023-28841 Référence CVE CVE-2023-28842 https://www.cve.org/CVERecord?id=CVE-2023-28842 Référence CVE CVE-2023-30861 https://www.cve.org/CVERecord?id=CVE-2023-30861 Référence CVE CVE-2023-31484 https://www.cve.org/CVERecord?id=CVE-2023-31484 Référence CVE CVE-2023-32681 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2022-23648 Référence CVE CVE-2022-29162 https://www.cve.org/CVERecord?id=CVE-2022-29162 Référence CVE CVE-2022-31030 https://www.cve.org/CVERecord?id=CVE-2022-31030 Référence CVE CVE-2022-42969 https://www.cve.org/CVERecord?id=CVE-2022-42969 Référence CVE CVE-2023-2253 https://www.cve.org/CVERecord?id=CVE-2023-2253 Référence CVE CVE-2023-25153 https://www.cve.org/CVERecord?id=CVE-2023-25153 Référence CVE CVE-2023-25173 https://www.cve.org/CVERecord?id=CVE-2023-25173 Référence CVE CVE-2023-25809 https://www.cve.org/CVERecord?id=CVE-2023-25809 Référence CVE CVE-2023-26136 https://www.cve.org/CVERecord?id=CVE-2023-26136 Référence CVE CVE-2023-26159 https://www.cve.org/CVERecord?id=CVE-2023-26159 Référence CVE CVE-2023-27561 https://www.cve.org/CVERecord?id=CVE-2023-27561 Référence CVE CVE-2023-28155 https://www.cve.org/CVERecord?id=CVE-2023-28155 Référence CVE CVE-2023-28642 https://www.cve.org/CVERecord?id=CVE-2023-28642 Référence CVE CVE-2023-28840 https://www.cve.org/CVERecord?id=CVE-2023-28840 Référence CVE CVE-2023-28841 https://www.cve.org/CVERecord?id=CVE-2023-28841 Référence CVE CVE-2023-28842 https://www.cve.org/CVERecord?id=CVE-2023-28842 Référence CVE CVE-2023-29827 https://www.cve.org/CVERecord?id=CVE-2023-29827 Référence CVE CVE-2023-39326 https://www.cve.org/CVERecord?id=

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

u 16 avril 2024 https://www.ibm.com/support/pages/node/7148426 Bulletin de sécurité IBM 7148517 du 17 avril 2024 https://www.ibm.com/support/pages/node/7148517 Bulletin de sécurité IBM 7148753 du 19 avril 2024 https://www.ibm.com/support/pages/node/7148753 Référence CVE CVE-2018-15494 https://www.cve.org/CVERecord?id=CVE-2018-15494 Référence CVE CVE-2018-6561 https://www.cve.org/CVERecord?id=CVE-2018-6561 Référence CVE CVE-2019-10785 https://www.cve.org/CVERecord?id=CVE-2019-10785 Référence CVE CVE-2020-4051 https://www.cve.org/CVERecord?id=CVE-2020-4051 Référence CVE CVE-2020-5259 https://www.cve.org/CVERecord?id=CVE-2020-5259 Référence CVE CVE-2023-26159 https://www.cve.org/CVERecord?id=CVE-2023-26159 Référence CVE CVE-2023-42282 https://www.cve.org/CVERecord?id=CVE-2023-42282 Référence CVE CVE-2023-44270 https://www.cve.org/CVERecord?id=CVE-2023-44270 Référence CVE CVE-2024-20918 https://www.cve.org/CVERecord?id=CVE-2024-20918 Référence CVE CVE-2024-20921 https://www.cve.org/CVERecord?id=CVE-2024-20921 Référence CVE CVE-2024-20926 https://www.cve.org/CVERecord?id=CVE-2024-20926 Référence CVE CVE-2024-20932 https://www.cve.org/CVERecord?id=CVE-2024-20932 Référence CVE CVE-2024-20945 https://www.cve.org/CVERecord?id=CVE-2024-20945 Référence CVE CVE-2024-20952 https://www.cve.org/CVERecord?id=

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

ecord?id=CVE-2022-46363 Référence CVE CVE-2022-46364 https://www.cve.org/CVERecord?id=CVE-2022-46364 Référence CVE CVE-2022-48560 https://www.cve.org/CVERecord?id=CVE-2022-48560 Référence CVE CVE-2022-48564 https://www.cve.org/CVERecord?id=CVE-2022-48564 Référence CVE CVE-2023-0286 https://www.cve.org/CVERecord?id=CVE-2023-0286 Référence CVE CVE-2023-1786 https://www.cve.org/CVERecord?id=CVE-2023-1786 Référence CVE CVE-2023-20569 https://www.cve.org/CVERecord?id=CVE-2023-20569 Référence CVE CVE-2023-22067 https://www.cve.org/CVERecord?id=CVE-2023-22067 Référence CVE CVE-2023-22081 https://www.cve.org/CVERecord?id=CVE-2023-22081 Référence CVE CVE-2023-26159 https://www.cve.org/CVERecord?id=CVE-2023-26159 Référence CVE CVE-2023-26604 https://www.cve.org/CVERecord?id=CVE-2023-26604 Référence CVE CVE-2023-27043 https://www.cve.org/CVERecord?id=CVE-2023-27043 Référence CVE CVE-2023-2828 https://www.cve.org/CVERecord?id=CVE-2023-2828 Référence CVE CVE-2023-28322 https://www.cve.org/CVERecord?id=CVE-2023-28322 Référence CVE CVE-2023-28486 https://www.cve.org/CVERecord?id=CVE-2023-28486 Référence CVE CVE-2023-28487 https://www.cve.org/CVERecord?id=CVE-2023-28487 Référence CVE CVE-2023-32681 https://www.cve.org/CVERecord?id=CVE-2023-32681 Référence CVE CVE-2023-3341 https://www.cve.org/CVERecord?id=CVE

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

ord?id=CVE-2023-24536 Référence CVE CVE-2023-24537 https://www.cve.org/CVERecord?id=CVE-2023-24537 Référence CVE CVE-2023-24538 https://www.cve.org/CVERecord?id=CVE-2023-24538 Référence CVE CVE-2023-24539 https://www.cve.org/CVERecord?id=CVE-2023-24539 Référence CVE CVE-2023-24540 https://www.cve.org/CVERecord?id=CVE-2023-24540 Référence CVE CVE-2023-2597 https://www.cve.org/CVERecord?id=CVE-2023-2597 Référence CVE CVE-2023-26048 https://www.cve.org/CVERecord?id=CVE-2023-26048 Référence CVE CVE-2023-26049 https://www.cve.org/CVERecord?id=CVE-2023-26049 Référence CVE CVE-2023-26115 https://www.cve.org/CVERecord?id=CVE-2023-26115 Référence CVE CVE-2023-26159 https://www.cve.org/CVERecord?id=CVE-2023-26159 Référence CVE CVE-2023-2650 https://www.cve.org/CVERecord?id=CVE-2023-2650 Référence CVE CVE-2023-27859 https://www.cve.org/CVERecord?id=CVE-2023-27859 Référence CVE CVE-2023-28319 https://www.cve.org/CVERecord?id=CVE-2023-28319 Référence CVE CVE-2023-28320 https://www.cve.org/CVERecord?id=CVE-2023-28320 Référence CVE CVE-2023-28321 https://www.cve.org/CVERecord?id=CVE-2023-28321 Référence CVE CVE-2023-28322 https://www.cve.org/CVERecord?id=CVE-2023-28322 Référence CVE CVE-2023-29258 https://www.cve.org/CVERecord?id=CVE-2023-29258 Référence CVE CVE-2023-29400 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-024863Follow Redirects project の Node.js 用 Follow Redirects におけるオープンリダイレクトの脆弱性

Follow Redirects project の Node.js 用 Follow Redirects には、オープンリダイレクトの脆弱性が存在します。

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
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
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 2 Jan 2024 · Last source change 3 Nov 2025, 21:47 UTC · CWE-20 · Improper Input Validation

CVE recordCVE.org · 5.2
CVSS sourceCNA
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-2024-0377
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 1.15.4 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    < 1.15.4 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2024-0377↗Red Hat Product Security security advisory↗CISA Vulnrichment SSVC evidence↗Patch or update reference↗Public exploit reference↗Public exploit 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-2023-26159 · cve.blacktree.nl