CVE-2025-15013VulnerabilityPublished 22 Dec 2025

CVE-2025-15013: floooh sokol · Stack-based Buffer Overflow

Affects floooh sokolSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

European organizations should take the following specific steps to mitigate CVE-2025-15013: 1) Immediately apply the patch identified by commit b95c5245ba357967220c9a860c7578a7487937b0 to all instances of the floooh sokol library in use. 2) Conduct an inventory of all software and embedded systems that incorporate sokol to identify affected deployments. 3) Restrict local access to systems running vulnerable versions, enforcing strict user permissions and limiting local accounts to trusted personnel only. 4) Implement monitoring and alerting for unusual local activity that could indicate exploitation attempts. 5) For development environments, ensure that build and deployment pipelines incorporate the patched library version and that developers are informed of the vulnerability. 6) Review and harden system configurations to minimize the impact of potential buffer overflow exploits, such as enabling stack canaries, DEP (Data Execution Prevention), and ASLR (Address Space Layout Randomization). 7) Educate local users about the risks of executing untrusted code or commands on affected systems. 8) Maintain up-to-date backups and incident response plans to quickly recover from any exploitation incidents. These targeted actions go beyond generic advice by focusing on local access control, patch management in rolling release contexts, and development pipeline hygiene.

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.

Impact

For European organizations, the impact of CVE-2025-15013 depends largely on their use of the floooh sokol graphics library. Organizations involved in software development, embedded systems, or graphics applications using sokol may face risks of local privilege escalation or denial of service due to memory corruption. This could lead to unauthorized code execution or system instability, affecting confidentiality, integrity, and availability of affected systems. In environments where multiple users share access or where local access controls are weak, the vulnerability could be exploited by malicious insiders or attackers who gain limited local access. Critical infrastructure or industrial control systems using embedded graphics components might also be at risk if they incorporate the vulnerable library. While remote exploitation is not possible, the presence of a public exploit increases the likelihood of targeted local attacks. The rolling release nature of the product means organizations must maintain vigilant patch management to avoid exposure. Overall, the threat is moderate but significant for sectors relying on the affected library within Europe.

Summary

CVE-2025-15013 is a stack-based buffer overflow vulnerability found in the _sg_validate_pipeline_desc function of the sokol_gfx.h header file, part of the floooh sokol graphics library. This vulnerability arises from improper validation or handling of pipeline descriptor data, allowing an attacker to overflow a buffer on the stack. The overflow can corrupt adjacent memory, potentially leading to arbitrary code execution, application crashes, or privilege escalation. The attack vector is local, requiring the attacker to have at least low-level privileges on the host system. No user interaction is needed once local access is obtained. The vulnerability affects versions up to commit 5d11344150973f15e16d3ec4ee7550a73fb995e0, but due to the rolling release model of the project, exact versioning is fluid. A patch has been committed (b95c5245ba357967220c9a860c7578a7487937b0) to fix the issue. Although no widespread exploitation is currently reported, a public exploit exists, increasing the risk of local attacks. The CVSS 4.8 rating reflects medium severity, considering the local attack vector and required privileges. The vulnerability primarily threatens applications or systems embedding the sokol graphics library, especially in development environments or embedded devices where local access is possible.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 22 Dec 2025, 05:13 UTC

Technical details

References

Community reviews

Related threats