SecPod

Learn Search

Search across all Learn content

← Back to Security Research
Squid Proxy Under Threat: Critical Bug Enables Remote Code Execution

Squid Proxy Under Threat: Critical Bug Enables Remote Code Execution

A critical vulnerability has been discovered in the Squid Web Proxy server, which could allow remote attackers to execute arbitrary code on affected systems. This vulnerability affects multiple versions and may impact many systems relying on Squid for caching and proxy functionality.

Aug 4, 2025By Rakshitha3 min read

A critical vulnerability has been discovered in the Squid Web Proxy server, which could allow remote attackers to execute arbitrary code on affected systems. This vulnerability affects multiple versions and may impact many systems relying on Squid for caching and proxy functionality.

Vulnerability Details

  • CVE-ID: CVE-2025-54574
  • CVSS Score: 9.3 (Critical) 
  • EPSS Score: 0.93%
  • Vulnerability: Heap Buffer Overflow vulnerability 
  • Affected Versions: Squid 6.3 and earlier

Infection Method

  • Attacker identifies a vulnerable Squid serverThe attacker scans the internet or internal networks to find Squid HTTP proxy servers running version 6.3 or earlier.
  • Target is confirmed as accessible.The attacker confirms that the proxy server accepts incoming client requests (i.e., is publicly or internally reachable).
  • Crafting a malicious URN requestA specially crafted URN (Uniform Resource Name) request is created. This request is designed to trigger the buffer management flaw in Squid’s URN handling logic.
  • Sending the malicious requestThe attacker sends the malicious URN request to the Squid proxy.
  • A heap buffer overflow is triggered.Squid processes the malformed URN without checking the proper bounds. Due to incorrect buffer management, a heap buffer overflow occurs in memory.
  • Execution of arbitrary codeThe attacker’s payload delivered via the overflow may overwrite function pointers or control data in memory, allowing remote code execution (RCE) on the proxy server.

Impact

Successful exploitation of this vulnerability can lead to remote code execution on affected Squid proxy servers without authentication or user interaction. Additionally, it may allow attackers to exfiltrate up to 4KB of heap memory, potentially exposing sensitive information such as security credentials or other confidential data stored in memory.

Mitigation & Recommendations

Organizations are strongly advised to upgrade to Squid version 6.4, which completely fixes this vulnerability. If upgrading is not immediately possible, a temporary workaround can be applied by disabling URN access via configuration changes. This can be achieved by adding ACL rules to block URN protocol requests, preventing exploitation until a proper update is deployed.

Instantly Fix Risks with Saner Patch Management

Saner patch management is a continuous, automated, and integrated software that instantly fixes risks exploited in the wild. The software supports major operating systems like Windows, Linux, and macOS, as well as 550+ third-party applications.

It also allows you to set up a safe testing area to test patches before deploying them in a primary production environment. Saner patch management additionally supports a patch rollback feature in case of patch failure or a system malfunction.

Experience the fastest and most accurate patching software here.

Featured Posts

Open WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels
WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels

CVE Research

WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels

Oct 1, 2026

Open OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure
OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure

CVE Research

OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure

Oct 1, 2026

Open Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions
Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions

CVE Research

Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions

Two critical vulnerabilities added to CISA KEV on September 24, 2026 reveal sharply different exploitation timelines. CVE-2026-71362 saw publicly documented exploitation roughly one day after Adobe's patch release, while CVE-2026-5430 had a 133-day vendor-remediation-to-observed-exploitation interval.

Oct 1, 2026

Open Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026
Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026

CVE Research

Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026

Three Linux kernel vulnerabilities entered CISA’s KEV catalog on September 18, 2026, although their Linux 6.12 fixes were available 91–386 days earlier. This analysis separates patch availability, CVE publication, and known-exploitation status without treating KEV dates as first-attack dates.

Sep 28, 2026