{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34391 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-34391 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34391 is a medium-severity vulnerability in fleetdm fleet, published on 27 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-34391 and fix it if it is affected.\n\nWhat it is: CVE-2026-34391 is a medium-severity vulnerability in fleetdm fleet, published on 27 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-34391 in the wild and no public exploit code.\n\nAffected product: fleetdm fleet. 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-34391/ (Markdown: https://insights.sbomify.com/CVE-2026-34391/index.md)","id":"CVE-2026-34391","markdown":"https://insights.sbomify.com/CVE-2026-34391/index.md","name":"CVE-2026-34391","record":{"aliases":["GHSA-wg7j-pcc3-h4rh"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Device management software","requires_auth":"none","summary":"A malicious enrolled device can access MDM commands intended for other devices, exposing sensitive configuration data like WiFi credentials and VPN secrets.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"fleet","vendor":"fleetdm"}],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-488","name":"Exposure of Data Element to Wrong Session"}],"description":"Fleet is open source device management software. Prior to 4.81.1, a vulnerability in Fleet's Windows MDM command processing allows a malicious enrolled device to access MDM commands intended for other devices, potentially exposing sensitive configuration data such as WiFi credentials, VPN secrets, and certificate payloads across the entire Windows fleet. Version 4.81.1 patches the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Fleet Vulnerable to Windows MDM cross-device command disclosure","id":"CVE-2026-34391","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"LORIS has a path traversal in static router","id":"CVE-2026-34392"},"packages":[],"prev":{"headline":"MantisBT: Privilege Escalation from Manager to Administrator","id":"CVE-2026-34390"},"products":["fleet"],"published":"2026-03-27","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":"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-03-27","vendors":["fleetdm"]},"summary":"A malicious enrolled device can access MDM commands intended for other devices, exposing sensitive configuration data like WiFi credentials and VPN secrets.","url":"https://insights.sbomify.com/CVE-2026-34391/"}