{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-24186 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-24186 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-24186 is a high-severity unsafe deserialization vulnerability in NVIDIA FLARE SDK, published on 28 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24186 and fix it if it is affected.\n\nWhat it is: CVE-2026-24186 is a high-severity unsafe deserialization vulnerability in NVIDIA FLARE SDK, published on 28 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-24186 in the wild and no public exploit code.\n\nAffected product: NVIDIA FLARE SDK. 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-24186/ (Markdown: https://insights.sbomify.com/CVE-2026-24186/index.md)","id":"CVE-2026-24186","markdown":"https://insights.sbomify.com/CVE-2026-24186/index.md","name":"CVE-2026-24186","record":{"aliases":["GHSA-3468-q87c-9xhv"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"NVIDIA FLARE SDK","requires_auth":"low_privilege","summary":"An attacker can execute arbitrary code by sending a malicious FOBS-encoded message to the NVIDIA FLARE SDK.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"nvidia","cpe":[{"product":"nvflare","vendor":"nvidia"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"NVIDIA FLARE SDK  contains a vulnerability in FOBS, where an attacker may cause deserialization of untrusted data by sending a malicious FOBS- encoded message. A successful exploit of this vulnerability might lead to code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Deserialization in FLARE SDK","id":"CVE-2026-24186","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Use after free in GeForce","id":"CVE-2026-24187"},"packages":[],"prev":{"headline":"Auth bypass in NVOS","id":"CVE-2026-24185"},"products":["FLARE SDK"],"published":"2026-04-28","related":[{"cvss_score":9.8,"headline":"NVIDIA NVFlare Dashboard: Authorization bypass through user-controlled key via user management and authentication system","id":"CVE-2026-24178","kev_date_added":null,"published":"2026-04-28"},{"cvss_score":9.8,"headline":"NVFLARE unsafe deserialization due to Pickle","id":"CVE-2022-34668","kev_date_added":null,"published":"2022-08-29"},{"cvss_score":9.8,"headline":"Unsafe deserialisation in the PKI implementation scheme of NVFlare","id":"CVE-2022-31604","kev_date_added":null,"published":"2022-07-01"},{"cvss_score":9.8,"headline":"Unsafe yaml deserialization in NVFlare","id":"CVE-2022-31605","kev_date_added":null,"published":"2022-07-01"},{"cvss_score":6.5,"headline":"Path traversal in FLARE SDK","id":"CVE-2026-24204","kev_date_added":null,"published":"2026-04-28"}],"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":"total"},"state":"PUBLISHED","updated":"2026-04-29","vendors":["NVIDIA"]},"summary":"An attacker can execute arbitrary code by sending a malicious FOBS-encoded message to the NVIDIA FLARE SDK.","url":"https://insights.sbomify.com/CVE-2026-24186/"}