{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33515 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-33515 is a medium-severity vulnerability in Squid-Cache Squid, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33515 and fix it if it is affected.\n\nWhat it is: CVE-2026-33515 is a medium-severity vulnerability in Squid-Cache Squid, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33515 in the wild and no public exploit code.\n\nAffected product: Squid-Cache Squid. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33515/ (Markdown: https://insights.sbomify.com/CVE-2026-33515/index.md)","id":"CVE-2026-33515","markdown":"https://insights.sbomify.com/CVE-2026-33515/index.md","name":"CVE-2026-33515","record":{"aliases":["AZL-80765","CLSA-2026-1779462193","DEBIAN-CVE-2026-33515","GHSA-84p4-hcx7-jj7c","MINI-x22r-37qg-625w","UBUNTU-CVE-2026-33515"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Web caching proxy","requires_auth":"none","summary":"Remote attackers can read sensitive memory via invalid ICP requests in Squid if ICP support is explicitly enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"squid","vendor":"squid-cache"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1289","name":"Improper Validation of Unsafe Equivalence in Input"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Squid is a caching proxy for the Web. Prior to version 7.5, due to improper input validation, Squid is vulnerable to out of bounds read when handling ICP traffic. This problem allows a remote attacker to receive small amounts of memory potentially containing sensitive information when responding with errors to invalid ICP requests. This attack is limited to Squid deployments that explicitly enable ICP support (i.e. configure non-zero `icp_port`). This problem cannot be mitigated by denying ICP queries using `icp_access` rules. Version 7.5 contains a patch.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Squid has issues in ICP message handling","id":"CVE-2026-33515","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"squid-cache:squid","products":["squid-cache:squid"],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"xrdp: Pre-authentication out-of-bounds reads in RDP capability and channel parsers","id":"CVE-2026-33516"},"packages":[],"prev":{"headline":"Discourse: Information Disclosure in Form Template API Due to Missing Authorization","id":"CVE-2026-33514"},"products":["squid"],"published":"2026-03-26","related":[{"cvss_score":10,"headline":"Squid vulnerable to information disclosure via authentication credential leakage in error handling","id":"CVE-2025-62168","kev_date_added":null,"published":"2025-10-17"},{"cvss_score":9.3,"headline":"Squid's URN Handling can lead to Buffer Overflow","id":"CVE-2025-54574","kev_date_added":null,"published":"2025-08-01"},{"cvss_score":9.2,"headline":"Squid vulnerable to Denial of Service in ICP Request handling","id":"CVE-2026-33526","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":8.7,"headline":"Squid has Denial of Service in ICP Response handling","id":"CVE-2026-32748","kev_date_added":null,"published":"2026-03-26"},{"cvss_score":8.6,"headline":"SQUID-2023:10 Denial of Service in HTTP Request parsing","id":"CVE-2023-50269","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":8.6,"headline":"Denial of Service in HTTP Message Processing in Squid","id":"CVE-2023-49285","kev_date_added":null,"published":"2023-12-04"},{"cvss_score":8.6,"headline":"Denial of Service in Helper Process management","id":"CVE-2023-49286","kev_date_added":null,"published":"2023-12-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-26","vendors":["squid-cache"]},"summary":"Remote attackers can read sensitive memory via invalid ICP requests in Squid if ICP support is explicitly enabled.","url":"https://insights.sbomify.com/CVE-2026-33515/"}