What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
webpack-dev-middleware is affected if it uses a vulnerable release and a configured publicPath without a trailing slash. Upgrade to version 7.4.6 or later on the 7.x branch, or 8.3.0 or later on the 8.x branch, subject to your project’s compatibility requirements. The described file-disclosure scenario additionally depends on physical filesystem backing; this is a development-middleware issue, not a claim that every webpack deployment or production build is vulnerable.
Which versions are affected?
The coordinated GitLab Advisory Database record, published September 29, 2026, lists these ranges:
As an Amazon Associate I earn from qualifying purchases.
| Branch | Affected versions | Fixed release |
|---|---|---|
| 7.x | All versions before 7.4.6 | 7.4.6 |
| 8.x | 8.0.0 through versions before 8.3.0 | 8.3.0 |
Use the fixed release on the branch compatible with your project, or a later compatible release. The advisory does not list every project’s compatibility constraints, so confirm the upgrade against your dependency tree and build setup.
Free tools Windows power users keep installed
One-click scans. No signup required.
How does the path traversal work?
The vulnerability concerns a particular combination of URL-path handling and configuration. When publicPath is configured without a trailing slash, the middleware checks whether a request pathname starts with that value, then removes the prefix using its character length to derive a filesystem path. A crafted pathname can put .. inside a segment rather than presenting it as a whole path segment. The traversal guard can miss that form; after the fixed-offset slice, a parent-directory component can remain in the resulting path. The GitHub advisory GHSA-p3f5-w63m-mxph describes the mechanics and the relationship to the earlier issue.
#1 Best Overall
- Available with the Cloud Labs which provide a hands-on, immersive mock IT infrastructure enabling students to test their skills with realistic security scenarios
- New Chapter on detailing network topologies
- The Table of Contents has been fully restructured to offer a more logical sequencing of subject matter
- Introduces the basics of network security—exploring the details of firewall security and how VPNs operate
- Increased coverage on device implantation and configuration
In the scenario described by the advisory, disclosure requires the middleware to use a physical filesystem. It identifies writeToDisk: true and a custom outputFileSystem as relevant conditions. The advisory says traversal in this issue is limited to one directory above the intended output path. With the default in-memory filesystem, build output is held in memory rather than read from the physical filesystem implicated in that disclosure scenario.
What should maintainers do?
- Identify the installed version and branch. Check the resolved
webpack-dev-middlewaredependency, not only the version range declared directly in a manifest; a lockfile or another dependency may determine what is installed. - Upgrade to a fixed release. Choose 7.4.6 or later in the compatible 7.x line, or 8.3.0 or later in the compatible 8.x line. This is the direct software fix listed in the coordinated advisory.
- Review
publicPath. As a mitigation, make an explicitly configured path end in/. Red Hat also listsauto, which the GitHub advisory says resolves to/, as a setting not affected by this issue. Follow the relevant Red Hat CVE record and GitHub advisory for configuration context; configuration changes do not replace upgrading. - Review filesystem backing. Check whether
writeToDisk: trueor a custom physicaloutputFileSystemis used. Avoiding physical filesystem backing is among the mitigations listed by Red Hat, but whether that is practical depends on your development setup. - Check exposure and sensitive output. Review whether untrusted clients can reach the development middleware and what files are available around its intended output path. This is a prudent response to the documented remote information-disclosure impact, not evidence that a particular deployment was exploited.
What is the severity?
The coordinated GitLab advisory publishes a CVSS 3.1 rating of 7.4 (High), with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N. This is the advisory’s severity assessment; it is not an incident count or a measure of how often the vulnerable configuration is deployed.
Rank #2
- equipped with atom n2600 d2700 processor, compatible with many freebsd based router systems, linux distros, or win.os supported, easy configuration and management
- Please note, this is a barebone only. A system memory, a storage drive and an operating system are needed to complete this system
- 13-19 inches 1u, 50w power, with power cord, make sure to use a big brand memory and ssd/hdd with quality assurance
- Designed with console, 2 x usb, 4 x lan, vga, power switch, size at 290 x 180 x 44mm
- There are 2 inside reserved fans on chassis, which could be removed freely or be turned on in a high temperature environment to ensure the best function of the product
How is this different from CVE-2024-29180?
CVE-2026-76844 is described as an incomplete fix for CVE-2024-29180, but the two advisories describe different edge cases and have different fixed-version ranges. The earlier issue involved insufficient URL validation and percent-encoded traversal; its advisory lists fixes 7.1.0, 6.1.2, and 5.3.4. Do not use those older fixes as the remediation for CVE-2026-76844: its listed fixes are 7.4.6 and 8.3.0.
Publication-history context
The coordinated GitLab record says VulnCheck assigned and published CVE-2026-76844 on August 24, 2026, without prior coordination with the webpack maintainers or the OpenJS Foundation CNA, and that no fix was available at that time. That notice describes the issue’s pre-coordination history; the current coordinated record lists fixed releases.
Quick Recap
Rank #4
- Compact and Efficient Design: The FortiGate 40F is designed for small to mid-sized businesses and enterprise branch offices, featuring a compact, fanless desktop form factor that ensures quiet operation and minimizes space usage.
- Robust Connectivity Options: Equipped with 5 GE RJ45 ports, including 1 WAN port and 4 internal ports, this model provides essential connectivity and flexibility for various network configurations in a small-scale environment.
- High-Performance Security: Offers up to 1 Gbps IPS throughput and 600 Mbps threat protection throughput, using Fortinet’s purpose-built security processor technology to deliver industry-leading performance and protection for SSL encrypted traffic.
- Advanced Threat Protection: Integrated with Fortinet’s AI-powered FortiGuard Labs, the FortiGate 40F offers comprehensive cybersecurity, identifying and mitigating both known and unknown threats to maintain robust security across your network.
- Simplified Management and Deployment: Features a user-friendly management console that provides comprehensive network automation and visibility, coupled with Zero Touch Integration with Fortinet’s Security Fabric for easy deployment.
Rank #3
- SonicWall TZ270W Appliance Only - No Service Subscription (02-SSC-2823) - Combines enterprise-grade firewalling with integrated 802.11ac Wave 2 Wi-Fi to deliver secure wired and wireless connectivity in one compact device for small offices and clinics.
- Blocks zero-day threats and ransomware with Capture ATP sandboxing enhanced by RTDMI, plus IPS and anti-malware scanning for layered protection.
- Eliminates the need for separate access points in smaller spaces thanks to built-in high-speed wireless that is simple to deploy and manage.
- Supports VPN, SD-WAN, and TLS 1.3 decryption to secure hybrid cloud access and remote workers while maintaining usability and performance.
- Delivers gigabit performance with up to 750,000 concurrent connections to handle growth in users, devices, and SaaS applications.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
