{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-46333 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-46333 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-46333 is a high-severity vulnerability in vancluever z2d, published on 25 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-46333 and fix it if it is affected.\n\nWhat it is: CVE-2025-46333 is a high-severity vulnerability in vancluever z2d, published on 25 Apr 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-46333 in the wild and no public exploit code.\n\nAffected product: vancluever z2d. 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-2025-46333/ (Markdown: https://insights.sbomify.com/CVE-2025-46333/index.md)","id":"CVE-2025-46333","markdown":"https://insights.sbomify.com/CVE-2025-46333/index.md","name":"CVE-2025-46333","record":{"aliases":["GHSA-mm4c-p35v-7hx3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Zig 2D graphics library","requires_auth":"low_privilege","summary":"An integer overflow in z2d's stride calculation during anti-aliased rendering can cause memory corruption and potential code execution in optimized builds.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"z2d is a pure Zig 2D graphics library. Versions of z2d after `0.5.1` and up to and including `0.6.0`, when writing from one surface to another using `z2d.compositor.StrideCompositor.run`, and higher-level operations when the anti-aliasing mode is set to `.default` (such as `Context.fill`, `Context.stroke`, `painter.fill`, and `painter.stroke`), the source surface can be completely out-of-bounds on the x-axis, but not on the y-axis, by way of a negative offset. This results in an overflow of the value controlling the length of the stride. In non-safe optimization modes (consumers compiling with `ReleaseFast` or `ReleaseSmall`), this could potentially lead to invalid memory accesses or corruption.\n\nThis issue is patched in version `0.6.1`. Users on an untagged version after `v0.5.1` and before `v0.6.1` are advised to update to address the vulnerability. Those still on Zig `0.13.0` are recommended to downgrade to `v0.5.1`.","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":"z2d OOB composition could lead to invalid memory access and corruption","id":"CVE-2025-46333","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Git GUI malicious command injection on Windows","id":"CVE-2025-46334"},"packages":[],"prev":{"headline":"Information Disclosure via Flags override link","id":"CVE-2025-46332"},"products":["z2d"],"published":"2025-04-25","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-28","vendors":["vancluever"]},"summary":"An integer overflow in z2d's stride calculation during anti-aliased rendering can cause memory corruption and potential code execution in optimized builds.","url":"https://insights.sbomify.com/CVE-2025-46333/"}