{"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-24004 in the wild and no public exploit code.","fix":"Upgrade github.com/fleetdm/fleet/v4 to 4.80.1 or later.","what":"CVE-2026-24004 is a low-severity missing authorization vulnerability in fleetdm fleet, published on 26 Feb 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-24004 and fix it if it is affected.\n\nWhat it is: CVE-2026-24004 is a low-severity missing authorization vulnerability in fleetdm fleet, published on 26 Feb 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-24004 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-24004/ (Markdown: https://insights.sbomify.com/CVE-2026-24004/index.md)","id":"CVE-2026-24004","markdown":"https://insights.sbomify.com/CVE-2026-24004/index.md","name":"CVE-2026-24004","record":{"aliases":["GHSA-9pm7-6g36-6j78","GO-2026-4563"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Fleet MDM server","requires_auth":"none","summary":"Unauthenticated attackers can disenroll Android devices from Fleet MDM if Android MDM is enabled, causing management disruption.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"fleet","vendor":"fleetdm"}],"cvss":{"score":1.7,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Fleet is open source device management software. In versions prior to 4.80.1, a vulnerability in Fleet’s Android MDM Pub/Sub handling could allow unauthenticated requests to trigger device unenrollment events. This may result in unauthorized removal of individual Android devices from Fleet management. If Android MDM is enabled, an attacker could send a crafted request to the Android Pub/Sub endpoint to unenroll a targeted Android device from Fleet without authentication. This issue does not grant access to Fleet, allow execution of commands, or provide visibility into device data. Impact is limited to disruption of Android device management for the affected device. Version 4.80.1 fixes the issue. If an immediate upgrade is not possible, affected Fleet users should temporarily disable Android MDM.","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: Unauthenticated Android device disenrollment vulnerability via Pub/Sub endpoint","id":"CVE-2026-24004","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"OpenKruise PodProbeMarker is Vulnerable to SSRF via Unrestricted Host Field","id":"CVE-2026-24005"},"packages":[{"ecosystem":"Go","fixed":["4.80.1"],"introduced":["0"],"last_affected":[],"package":"github.com/fleetdm/fleet/v4","purl":null,"source":"GHSA-9pm7-6g36-6j78"},{"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-9pm7-6g36-6j78"},{"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-4563"}],"prev":{"headline":"EvseV2G has sequence state validation bypass","id":"CVE-2026-24003"},"products":["fleet"],"published":"2026-02-26","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["fleetdm"]},"summary":"Unauthenticated attackers can disenroll Android devices from Fleet MDM if Android MDM is enabled, causing management disruption.","url":"https://insights.sbomify.com/CVE-2026-24004/"}