# CVE-2025-15013: floooh sokol sokol_gfx.h _sg_validate_pipeline_desc stack-based overflow

> A stack-based buffer overflow in the sokol graphics library allows local attackers to execute arbitrary code or cause denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Dec 2025
- **Updated:** 22 Dec 2025
- **Also known as:** GHSA-ff2p-7h68-73qg

## What is CVE-2025-15013?

CVE-2025-15013 is a medium-severity memory corruption vulnerability in floooh sokol, published on 22 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was identified in floooh sokol up to 5d11344150973f15e16d3ec4ee7550a73fb995e0. The impacted element is the function _sg_validate_pipeline_desc in the library sokol_gfx.h. Such manipulation leads to stack-based buffer overflow. The attack must be carried out locally. The exploit is publicly available and might be used. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The name of the patch is b95c5245ba357967220c9a860c7578a7487937b0. It is best practice to apply a patch to resolve this issue.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-15013?


## How do I fix CVE-2025-15013?

No fix has been published for CVE-2025-15013 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-15013 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15013 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15013 and fix it if it is affected.

What it is: CVE-2025-15013 is a medium-severity memory corruption vulnerability in floooh sokol, published on 22 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15013 exists.

Affected product: floooh sokol. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-15013/ (Markdown: https://insights.sbomify.com/CVE-2025-15013/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15013
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15013
- OSV: https://osv.dev/vulnerability/CVE-2025-15013

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-15013/
Summaries are generated and may contain mistakes; the official description above is the record.