z2d OOB composition could lead to invalid memory access and corruption
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. This 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`.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2025-46333
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 19:24 UTC · Revision 1
Source evidence
z2d OOB composition could lead to invalid memory access and corruption
core-osv · Original sourcePublished 25 Apr 2025, 20:20 UTC
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. This 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`.
osv:CVE-2025-46333
Complete source record
{
"id": "e8d3c570760707c132f6a3b9cd3a4dd3feefec1b529c231e216da86f623bdfb9",
"url": "https://osv.dev/vulnerability/CVE-2025-46333",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "z2d OOB composition could lead to invalid memory access and corruption",
"summary": "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. This 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`.",
"evidence": "osv:CVE-2025-46333",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2025-46333",
"aliases": [
"CVE-2025-46333",
"GHSA-mm4c-p35v-7hx3"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/vancluever/z2d",
"type": "GIT",
"events": [
{
"introduced": "a99bf85d38d716d30b79c3546e7063af2e861f49"
},
{
"last_affected": "5d41e5ed8f388fc3fa39210cc93ee5584e7d7d6f"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0.5.1"
},
{
"last_affected": "0.6.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
}
]
}
}
],
"versions": [
"v0.6.0",
"v0.5.1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-46333.json"
}
}
],
"modified": "2026-10-28T02:30:38.606384897Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/46xxx/CVE-2025-46333.json",
"https://github.com/vancluever/z2d/security/advisories/GHSA-mm4c-p35v-7hx3",
"https://nvd.nist.gov/vuln/detail/CVE-2025-46333",
"https://github.com/vancluever/z2d/issues/104",
"https://github.com/vancluever/z2d/issues/105"
],
"provider_metadata": {
"cwe_ids": [
"CWE-119",
"CWE-122",
"CWE-190"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/46xxx/CVE-2025-46333.json"
}
},
"related_cves": [
{
"value": "CVE-2025-46333",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 506138,
"published_at": "2025-04-25T20:20:22.202+00:00"
}