{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9521 exists.","fix":"No fix has been published for CVE-2026-9521 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9521 is a medium-severity unsafe deserialization vulnerability in fraillt bitsery, published on 26 May 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-9521 and fix it if it is affected.\n\nWhat it is: CVE-2026-9521 is a medium-severity unsafe deserialization vulnerability in fraillt bitsery, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9521 exists.\n\nAffected product: fraillt bitsery. 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-9521/ (Markdown: https://insights.sbomify.com/CVE-2026-9521/index.md)","id":"CVE-2026-9521","markdown":"https://insights.sbomify.com/CVE-2026-9521/index.md","name":"CVE-2026-9521","record":{"aliases":["GHSA-xvwh-vh35-wwv2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"C++ serialization library","requires_auth":"none","summary":"Remote attackers can exploit improper input validation in the bitsery library's smart pointer deserialization to potentially execute arbitrary code.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-1287","name":"Improper Validation of Specified Type of Input"}],"description":"A security vulnerability has been detected in fraillt bitsery up to 5.2.4. Affected is the function loadFromSharedState in the library include/bitsery/ext/std_smart_ptr.h. Such manipulation leads to improper validation of specified type of input. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 5.2.5 is able to address this issue. The name of the patch is 66d16516e24893bebc1c8af52bf2fe9ad0735061. Upgrading the affected component is advised.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"fraillt bitsery std_smart_ptr.h loadFromSharedState improper validation of specified type of input","id":"CVE-2026-9521","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Missing authorization in Server","id":"CVE-2026-9522"},"packages":[],"prev":{"headline":"blitz-js blitz Sign-in LoginForm.tsx cross site scripting","id":"CVE-2026-9520"},"products":["bitsery"],"published":"2026-05-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-26","vendors":["fraillt"]},"summary":"Remote attackers can exploit improper input validation in the bitsery library's smart pointer deserialization to potentially execute arbitrary code.","url":"https://insights.sbomify.com/CVE-2026-9521/"}