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

webpack buildHttp: allowedUris allow-list bypass via URL userinfo (@) leading to build-time SSRF behavior

webpack · webpack

Official source article: GitHub GHSA-8FGC-7CC6-RX7X ↗. Check the applicable product and release in the original source.

3.7LowCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Low 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 2 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 severityLowOperational priority:Medium, raised one band.upgradedsince 6 Feb 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 0.23% 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 webpack webpack 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: As exposure requiresRemediation target: Within 365 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 2 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.

5 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 · sourcenode-webpackAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcenode-webpackAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcenode-webpackVendor fix publishedDebian records a fixed source-package version for this release.5.105.4+dfsg1+~cs15.13.23-2Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcenode-webpackVendor fix publishedDebian records a fixed source-package version for this release.5.105.4+dfsg1+~cs15.13.23-2Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivenode-webpackUnder 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
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
npmwebpack>= 5.49.0, <= 5.104.05.104.1GitHub advisory ↗upstream repository advisory · 6 Feb 2026
npmwebpackSEMVER: introduced 5.49.0; fixed 5.104.15.104.1OSV 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-2025-68458 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitywebpack: webpack buildHttp: allowedUris allow-list bypass via URL userinfo (@) leading to build-time SSRF behavior
127 known affected

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

  • io.cryostat-cryostat as a component of Cryostat 4
  • gatekeeper/gatekeeper-rhel9 as a component of Gatekeeper 3
  • openshift-logging/elasticsearch-operator-bundle as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/elasticsearch-proxy-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/elasticsearch-rhel9-operator as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/elasticsearch6-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/kibana6-rhel8 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/logging-curator5-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • openshift-logging/logging-view-plugin-rhel9 as a component of Logging Subsystem for Red Hat OpenShift
  • network-observability/network-observability-console-plugin-compat-rhel9 as a component of Network Observability Operator
  • workload-availability/node-healthcheck-must-gather-rhel9 as a component of Node HealthCheck Operator
  • workload-availability/node-healthcheck-operator-bundle as a component of Node HealthCheck Operator
Summary
An SSRF flaw has been discovered in Webpack. When experiments.buildHttp is enabled, webpack’s HTTP(S) resolver (HttpUriPlugin) can be bypassed to fetch resources from hosts outside allowedUris by using crafted URLs that include userinfo (username:password@host). If allowedUris enforcement relies on a raw string prefix check (e.g., uri.startsWith(allowed)), a URL that looks allow-listed can pass validation while the actual network request is sent to a different authority/host after URL parsing. This is a policy/allow-list bypass that enables build-time SSRF behavior (outbound requests from the build machine to internal-only endpoints, depending on network access) and untrusted content inclusion (the fetched response is treated as module source and bundled).
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.18/html/updating_openshift_data_foundation/updating-ocs-to-odf_rhodf
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-2025-206877

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

Low 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 2 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

Webpack is a module bundler. From version 5.49.0 to before 5.104.1, when experiments.buildHttp is enabled, webpack’s HTTP(S) resolver (HttpUriPlugin) can be bypassed to fetch resources from hosts outside allowedUris by using crafted URLs that include userinfo (username:password@host). If allowedUris enforcement relies on a raw string prefix check (e.g., uri.startsWith(allowed)), a URL that looks allow-listed can pass validation while the actual network request is sent to a different authority/host after URL parsing. This is a policy/allow-list bypass that enables build-time SSRF behavior (outbound requests from the build machine to internal-only endpoints, depending on network access) and untrusted content inclusion (the fetched response is treated as module source and bundled). This issue has been patched in version 5.104.1.

What

Webpack is a module bundler. From version 5.49.0 to before 5.104.1, when experiments.buildHttp is enabled, webpack’s HTTP(S) resolver (HttpUriPlugin) can be bypassed to fetch resources from hosts outside allowedUris by using crafted URLs that include userinfo (username:password@host). If allowedUris enforcement relies on a raw string prefix check (e.g., uri.startsWith(allowed)), a URL that looks allow-listed can pass validation while the actual network request is sent to a different authority/host after URL parsing. This is a policy/allow-list bypass that enables build-time SSRF behavior (outbound requests from the build machine to internal-only endpoints, depending on network access) and untrusted content inclusion (the fetched response is treated as module source and bundled). This issue has been patched in version 5.104.1.

Why

The server follows an attacker-influenced destination, allowing requests to systems or services the attacker cannot reach directly.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Webpack is a module bundler. From version 5.49.0 to before 5.104.1, when experiments.buildHttp is enabled, webpack’s HTTP(S) resolver (HttpUriPlugin) can be bypassed to fetch resources from hosts outside allowedUris by using crafted URLs that include userinfo (username:password@host). If allowedUris enforcement relies on a raw string prefix check (e.g., uri.startsWith(allowed)), a URL that looks allow-listed can pass validation while the actual network request is sent to a different authority/host after URL parsing. This is a policy/allow-list bypass that enables build-time SSRF behavior (outbound requests from the build machine to internal-only endpoints, depending on network access) and untrusted content inclusion (the fetched response is treated as module source and bundled). This issue has been patched in version 5.104.1.

Why

The server follows an attacker-influenced destination, allowing requests to systems or services the attacker cannot reach directly.

How

An attacker operating through a network path may attempt exploitation with low privileges. 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.
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 → Server-Side Request Forgery (SSRF) → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
Required interaction required
Attack complexity
High: exploitation depends on specific conditions
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-918 ↗

CWE-918: Server-Side Request Forgery (SSRF). The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

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:H/PR:L/UI:R/S:U/C:L/I:L/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.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.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.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.
NetworkCWE-918Public exploit reference
A

Official authority intelligence

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

Cyber Security Agency of Singapore · English · CSA-SB-20260211Security Bulletin 11 Feb 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 11 Feb 2026, published on 11 February 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

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

ord?id=CVE-2025-58754 Référence CVE CVE-2025-5889 https://www.cve.org/CVERecord?id=CVE-2025-5889 Référence CVE CVE-2025-59250 https://www.cve.org/CVERecord?id=CVE-2025-59250 Référence CVE CVE-2025-59471 https://www.cve.org/CVERecord?id=CVE-2025-59471 Référence CVE CVE-2025-62718 https://www.cve.org/CVERecord?id=CVE-2025-62718 Référence CVE CVE-2025-64718 https://www.cve.org/CVERecord?id=CVE-2025-64718 Référence CVE CVE-2025-64756 https://www.cve.org/CVERecord?id=CVE-2025-64756 Référence CVE CVE-2025-68157 https://www.cve.org/CVERecord?id=CVE-2025-68157 Référence CVE CVE-2025-68161 https://www.cve.org/CVERecord?id=CVE-2025-68161 Référence CVE CVE-2025-68458 https://www.cve.org/CVERecord?id=CVE-2025-68458 Référence CVE CVE-2025-69873 https://www.cve.org/CVERecord?id=CVE-2025-69873 Référence CVE CVE-2025-71132 https://www.cve.org/CVERecord?id=CVE-2025-71132 Référence CVE CVE-2025-71176 https://www.cve.org/CVERecord?id=CVE-2025-71176 Référence CVE CVE-2025-7783 https://www.cve.org/CVERecord?id=CVE-2025-7783 Référence CVE CVE-2026-0540 https://www.cve.org/CVERecord?id=CVE-2026-0540 Référence CVE CVE-2026-0636 https://www.cve.org/CVERecord?id=CVE-2026-0636 Référence CVE CVE-2026-10723 https://www.cve.org/CVERecord?id=CVE-2026-10723 Référence CVE CVE-2026-10805 https://www.cve.org/CVERecord?id=CVE-20

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

ord?id=CVE-2025-62718 Référence CVE CVE-2025-6493 https://www.cve.org/CVERecord?id=CVE-2025-6493 Référence CVE CVE-2025-66221 https://www.cve.org/CVERecord?id=CVE-2025-66221 Référence CVE CVE-2025-66418 https://www.cve.org/CVERecord?id=CVE-2025-66418 Référence CVE CVE-2025-66471 https://www.cve.org/CVERecord?id=CVE-2025-66471 Référence CVE CVE-2025-67724 https://www.cve.org/CVERecord?id=CVE-2025-67724 Référence CVE CVE-2025-67725 https://www.cve.org/CVERecord?id=CVE-2025-67725 Référence CVE CVE-2025-67726 https://www.cve.org/CVERecord?id=CVE-2025-67726 Référence CVE CVE-2025-68157 https://www.cve.org/CVERecord?id=CVE-2025-68157 Référence CVE CVE-2025-68458 https://www.cve.org/CVERecord?id=CVE-2025-68458 Référence CVE CVE-2025-68470 https://www.cve.org/CVERecord?id=CVE-2025-68470 Référence CVE CVE-2025-69873 https://www.cve.org/CVERecord?id=CVE-2025-69873 Référence CVE CVE-2025-71176 https://www.cve.org/CVERecord?id=CVE-2025-71176 Référence CVE CVE-2026-0540 https://www.cve.org/CVERecord?id=CVE-2026-0540 Référence CVE CVE-2026-10535 https://www.cve.org/CVERecord?id=CVE-2026-10535 Référence CVE CVE-2026-10842 https://www.cve.org/CVERecord?id=CVE-2026-10842 Référence CVE CVE-2026-11595 https://www.cve.org/CVERecord?id=CVE-2026-11595 Référence CVE CVE-2026-11708 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0500Multiples vulnérabilités dans VMware Tanzu

d?id=CVE-2025-62718 Référence CVE CVE-2025-64718 https://www.cve.org/CVERecord?id=CVE-2025-64718 Référence CVE CVE-2025-65995 https://www.cve.org/CVERecord?id=CVE-2025-65995 Référence CVE CVE-2025-66236 https://www.cve.org/CVERecord?id=CVE-2025-66236 Référence CVE CVE-2025-66614 https://www.cve.org/CVERecord?id=CVE-2025-66614 Référence CVE CVE-2025-67721 https://www.cve.org/CVERecord?id=CVE-2025-67721 Référence CVE CVE-2025-67735 https://www.cve.org/CVERecord?id=CVE-2025-67735 Référence CVE CVE-2025-68157 https://www.cve.org/CVERecord?id=CVE-2025-68157 Référence CVE CVE-2025-68161 https://www.cve.org/CVERecord?id=CVE-2025-68161 Référence CVE CVE-2025-68458 https://www.cve.org/CVERecord?id=CVE-2025-68458 Référence CVE CVE-2025-68470 https://www.cve.org/CVERecord?id=CVE-2025-68470 Référence CVE CVE-2025-68675 https://www.cve.org/CVERecord?id=CVE-2025-68675 Référence CVE CVE-2025-69873 https://www.cve.org/CVERecord?id=CVE-2025-69873 Référence CVE CVE-2025-7783 https://www.cve.org/CVERecord?id=CVE-2025-7783 Référence CVE CVE-2025-7962 https://www.cve.org/CVERecord?id=CVE-2025-7962 Référence CVE CVE-2025-8885 https://www.cve.org/CVERecord?id=CVE-2025-8885 Référence CVE CVE-2025-8916 https://www.cve.org/CVERecord?id=CVE-2025-8916 Référence CVE CVE-2025-9624 https://www.cve.org/CVERecord?id=CVE-2025-

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-003686webpackにおけるサーバサイドのリクエストフォージェリの脆弱性

Webpackはモジュールバンドラーです。バージョン5.49.0から5.104.1未満の間、experiments.buildHttpが有効な場合、WebpackのHTTP(S)リゾルバ（HttpUriPlugin）は、userinfo（username:password@host）を含む細工されたURLを使用することで、allowedUrisの外部ホストからリソースを取得可能でした。allowedUrisの適用は生の文字列の接頭辞チェック（例：uri.startsWith(allowed)）に依存しており、許可されたかのように見えるURLが検証を通過しても、実際のネットワークリクエストはURL解析後に異なる権限やホストへ送信されてしまいます。これはポリシーや許可リストの回避を招き、ビルド時のSSRF動作（ビルドマシンから内部限定エンドポイントへのアウトバウンドリクエスト、ネットワークアクセスに依存）や信頼できないコンテンツの取り込み（取得したレスポンスがモジュールソースとして扱われバンドルに含まれる）を可能にしました。この問題はバージョン5.104.1で修正されています。

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 5 Feb 2026 · Last source change 6 Feb 2026, 20:26 UTC · CWE-918 · Server-Side Request Forgery (SSRF)

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-2025-206877
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.49.0, < 5.104.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    >= 5.49.0, < 5.104.1 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://docs.redhat.com/en/documentation/red_hat_openshift_data_foundation/4.18/html/updating_openshift_data_foundation/updating-ocs-to-odf_rhodf
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2025-206877↗Red Hat Product Security security advisory↗CISA Vulnrichment SSVC evidence↗Public exploit reference · GitHub GHSA-8FGC-7CC6-RX7X↗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-2025-68458 · cve.blacktree.nl