{"answers":{"affected":"3 open source packages ship an affected version, including github.com/fleetdm/fleet/v4. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-24000 in the wild and no public exploit code.","fix":"Upgrade github.com/fleetdm/fleet/v4 to 4.80.1 or later.","what":"CVE-2026-24000 is a medium-severity vulnerability in fleetdm fleet, published on 14 May 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-24000 and fix it if it is affected.\n\nWhat it is: CVE-2026-24000 is a medium-severity vulnerability in fleetdm fleet, published on 14 May 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-24000 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.80.1\n- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.80.1\n- github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.80.1\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-24000/ (Markdown: https://insights.sbomify.com/CVE-2026-24000/index.md)","id":"CVE-2026-24000","markdown":"https://insights.sbomify.com/CVE-2026-24000/index.md","name":"CVE-2026-24000","record":{"aliases":["GHSA-j8h8-75h3-jg53","GO-2026-5455"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fleet device management","requires_auth":"none","summary":"Attackers can bypass IP-based rate limits in Fleet by spoofing client IP headers, facilitating brute-force attacks against authentication endpoints.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"fleet","vendor":"fleetdm"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"Fleet is open source device management software. Prior to version 4.80.1, Fleet trusted client-supplied IP address headers when determining the source IP for incoming requests. This allowed authenticated and unauthenticated clients to spoof their apparent IP address and bypass per-IP rate limiting controls. Fleet determines a client’s public IP address using HTTP headers such as X-Forwarded-For, X-Real-IP, and/or True-Client-IP. These headers were trusted without validation. An attacker could supply arbitrary values in these headers, causing Fleet to treat each request as originating from a different IP address. This could allow an attacker to bypass per-IP rate limits and increase the effectiveness of brute-force or password-spraying attempts against authentication endpoints. This issue does not allow authentication bypass, privilege escalation, data exposure, or remote code execution on its own. Version 4.80.1 contains a patch. As a workaround, run Fleet behind a trusted reverse proxy or load balancer that overwrites client IP headers.","ecosystems":["Go"],"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":"Fleet has a rate limiting bypass via untrusted client IP headers","id":"CVE-2026-24000","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"jsdiff has a Denial of Service vulnerability in parsePatch and applyPatch","id":"CVE-2026-24001"},"packages":[{"ecosystem":"Go","fixed":["4.80.1"],"introduced":["0"],"last_affected":[],"package":"github.com/fleetdm/fleet/v4","purl":null,"source":"GHSA-j8h8-75h3-jg53"},{"ecosystem":"Go","fixed":["4.80.1"],"introduced":["0"],"last_affected":[],"package":"github.com/fleetdm/fleet/v4","purl":"pkg:golang/github.com/fleetdm/fleet/v4","source":"GHSA-j8h8-75h3-jg53"},{"ecosystem":"Go","fixed":["4.80.1"],"introduced":["0"],"last_affected":[],"package":"github.com/fleetdm/fleet/v4","purl":"pkg:golang/github.com/fleetdm/fleet/v4","source":"GO-2026-5455"}],"prev":{"headline":"Fleet: Device lock PIN can be predicted if lock time is known","id":"CVE-2026-23999"},"products":["fleet"],"published":"2026-05-14","related":[{"cvss_score":10,"headline":"SAML authentication vulnerability in Fleet","id":"CVE-2020-26276","kev_date_added":null,"published":"2020-12-17"},{"cvss_score":9.3,"headline":"Fleet before 4.87.0 Authentication Bypass via Device Identifiers","id":"CVE-2026-103264","kev_date_added":null,"published":"2026-10-01"},{"cvss_score":9.3,"headline":"Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment","id":"CVE-2026-23518","kev_date_added":null,"published":"2026-01-21"},{"cvss_score":8.7,"headline":"Fleet server may terminate unexpectedly when handling certain gRPC requests","id":"CVE-2026-26062","kev_date_added":null,"published":"2026-05-14"},{"cvss_score":8.7,"headline":"Fleet's unbounded request body read allows remote Denial of Service","id":"CVE-2026-26061","kev_date_added":null,"published":"2026-03-27"},{"cvss_score":8.2,"headline":"Fleet has a Windows MDM management endpoint authentication bypass","id":"CVE-2026-23998","kev_date_added":null,"published":"2026-05-14"},{"cvss_score":8.2,"headline":"Fleet Windows MDM Azure AD JWT Authentication Bypass","id":"CVE-2026-24899","kev_date_added":null,"published":"2026-05-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"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-05-14","vendors":["fleetdm"]},"summary":"Attackers can bypass IP-based rate limits in Fleet by spoofing client IP headers, facilitating brute-force attacks against authentication endpoints.","url":"https://insights.sbomify.com/CVE-2026-24000/"}