{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-103513 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-103513 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-103513 is a critical memory corruption vulnerability in Apache DataSketches, published on 10 Oct 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-103513 and fix it if it is affected.\n\nWhat it is: CVE-2026-103513 is a critical memory corruption vulnerability in Apache DataSketches, published on 10 Oct 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-103513 in the wild and no public exploit code.\n\nAffected product: Apache DataSketches. 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-103513/ (Markdown: https://insights.sbomify.com/CVE-2026-103513/index.md)","id":"CVE-2026-103513","markdown":"https://insights.sbomify.com/CVE-2026-103513/index.md","name":"CVE-2026-103513","record":{"aliases":["GHSA-2w73-5h25-v3cg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"C++ data sketching library","requires_auth":"none","summary":"Attackers can trigger memory corruption and potential code execution by providing crafted serialized CPC sketches to applications using the vulnerable C++ library.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","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-787","name":"Out-of-bounds Write"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Out-of-bounds read and write in the CPC sketch deserialization of Apache DataSketches C++ (repo: datasketches-cpp).\n\nA crafted serialized CPC sketch passed to cpc_sketch::deserialize(), from either a byte buffer or a stream, can cause the decompressor to read past the end of the compressed data, because the read position was only checked after decoding finished. In the hybrid flavor, it can also cause a write outside an internal heap buffer, because decoded row indices were not validated. Several other header fields and decoded values, including lg_k, were also not validated. This can corrupt heap memory, causing a crash and potentially enabling further exploitation.\n\nThis issue affects Apache DataSketches C++: from 2.0.0-incubating before 5.3.0. Only applications that deserialize CPC sketches from untrusted sources are affected.\n\nUsers are recommended to upgrade to version 5.3.0, which fixes this 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":"Memory corruption in Apache DataSketches","id":"CVE-2026-103513","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"WP 2FA \u003c 4.1.0 - Two-Factor Authentication Bypass via TOTP Code Replay","id":"CVE-2026-103514"},"packages":[],"prev":{"headline":"Ticket host-binding bypass via spoofed client IP in P4Search","id":"CVE-2026-103512"},"products":["Apache DataSketches"],"published":"2026-10-10","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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Apache Software Foundation"]},"summary":"Attackers can trigger memory corruption and potential code execution by providing crafted serialized CPC sketches to applications using the vulnerable C++ library.","url":"https://insights.sbomify.com/CVE-2026-103513/"}