{"answers":{"affected":"3 open source packages ship an affected version, including nvflare. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-24178 in the wild and no public exploit code.","fix":"Upgrade nvflare to 2.7.2 or later.","what":"CVE-2026-24178 is a critical authentication bypass vulnerability in NVIDIA FLARE SDK, published on 28 Apr 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-24178 and fix it if it is affected.\n\nWhat it is: CVE-2026-24178 is a critical authentication bypass vulnerability in NVIDIA FLARE SDK, published on 28 Apr 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-24178 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nvflare (PyPI): affected all versions; fixed in 2.7.2\n- nvflare (PyPI): affected all versions; fixed in 2.7.2\n- nvflare (PyPI): affected all versions; fixed in 2.7.2\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-24178/ (Markdown: https://insights.sbomify.com/CVE-2026-24178/index.md)","id":"CVE-2026-24178","markdown":"https://insights.sbomify.com/CVE-2026-24178/index.md","name":"CVE-2026-24178","record":{"aliases":["GHSA-jqp3-qrgh-4846","PYSEC-2026-100"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"NVIDIA NVFlare Dashboard","requires_auth":"none","summary":"Unauthenticated attackers can bypass authorization in NVIDIA NVFlare Dashboard to escalate privileges, execute code, and access or modify data.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"nvidia","cpe":[{"product":"nvflare","vendor":"nvidia"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"NVIDIA NVFlare Dashboard contains a vulnerability in the user management and authentication system where an unauthenticated attacker may cause authorization bypass through user-controlled key. A successful exploit of this vulnerability may lead to privilege escalation, data tampering, information disclosure, code execution, and denial of service.","ecosystems":["PyPI"],"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":"NVIDIA NVFlare Dashboard: Authorization bypass through user-controlled key via user management and authentication system","id":"CVE-2026-24178","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Memory corruption in DALI","id":"CVE-2026-24180"},"packages":[{"ecosystem":"PyPI","fixed":["2.7.2"],"introduced":["0"],"last_affected":[],"package":"nvflare","purl":null,"source":"GHSA-jqp3-qrgh-4846"},{"ecosystem":"PyPI","fixed":["2.7.2"],"introduced":["0"],"last_affected":[],"package":"nvflare","purl":"pkg:pypi/nvflare","source":"GHSA-jqp3-qrgh-4846"},{"ecosystem":"PyPI","fixed":["2.7.2"],"introduced":["0"],"last_affected":[],"package":"nvflare","purl":"pkg:pypi/nvflare","source":"PYSEC-2026-100"}],"prev":{"headline":"Missing authorization in KAI Scheduler","id":"CVE-2026-24177"},"products":["FLARE SDK"],"published":"2026-04-28","related":[{"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":8.8,"headline":"Deserialization in FLARE SDK","id":"CVE-2026-24186","kev_date_added":null,"published":"2026-04-28"},{"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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"total"},"state":"PUBLISHED","updated":"2026-04-29","vendors":["NVIDIA"]},"summary":"Unauthenticated attackers can bypass authorization in NVIDIA NVFlare Dashboard to escalate privileges, execute code, and access or modify data.","url":"https://insights.sbomify.com/CVE-2026-24178/"}