{"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-23999 in the wild and no public exploit code.","fix":"Upgrade github.com/fleetdm/fleet/v4 to 4.80.1 or later.","what":"CVE-2026-23999 is a low-severity vulnerability in fleetdm fleet, published on 26 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-23999 and fix it if it is affected.\n\nWhat it is: CVE-2026-23999 is a low-severity vulnerability in fleetdm fleet, published on 26 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-23999 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-23999/ (Markdown: https://insights.sbomify.com/CVE-2026-23999/index.md)","id":"CVE-2026-23999","markdown":"https://insights.sbomify.com/CVE-2026-23999/index.md","name":"CVE-2026-23999","record":{"aliases":["GHSA-ppwx-5jq7-px2w","GO-2026-4564"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Device management software","requires_auth":"none","summary":"Attackers with physical access and timing knowledge can predict device lock PINs due to weak entropy, bypassing lock controls.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"fleet","vendor":"fleetdm"}],"cvss":{"score":0.6,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"Fleet is open source device management software. In versions prior to 4.80.1, Fleet generated device lock and wipe PINs using a predictable algorithm based solely on the current Unix timestamp. Because no secret key or additional entropy was used, the resulting PIN could potentially be derived if the approximate time the device was locked is known. Fleet’s device lock and wipe commands generate a 6-digit PIN that is displayed to administrators for unlocking a device. In affected versions, this PIN was deterministically derived from the current timestamp. An attacker with physical possession of a locked device and knowledge of the approximate time the lock command was issued could theoretically predict the correct PIN within a limited search window. However, successful exploitation is constrained by multiple factors: Physical access to the device is required, the approximate lock time must be known, the operating system enforces rate limiting on PIN entry attempts, attempts would need to be spread over, and device wipe operations would typically complete before sufficient attempts could be made. As a result, this issue does not allow remote exploitation, fleet-wide compromise, or bypass of Fleet authentication controls. Version 4.80.1 contains a patch. No known workarounds are available.","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: Device lock PIN can be predicted if lock time is known","id":"CVE-2026-23999","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Fleet has a rate limiting bypass via untrusted client IP headers","id":"CVE-2026-24000"},"packages":[{"ecosystem":"Go","fixed":["4.80.1"],"introduced":["0"],"last_affected":[],"package":"github.com/fleetdm/fleet/v4","purl":null,"source":"GHSA-ppwx-5jq7-px2w"},{"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-ppwx-5jq7-px2w"},{"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-4564"}],"prev":{"headline":"Fleet has a Windows MDM management endpoint authentication bypass","id":"CVE-2026-23998"},"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":"Attackers with physical access and timing knowledge can predict device lock PINs due to weak entropy, bypassing lock controls.","url":"https://insights.sbomify.com/CVE-2026-23999/"}