# CVE-2025-11015: OGRECave Ogre OgreSTBICodec.cpp encode mismatched memory management routines

> Local attackers can exploit mismatched memory management in the STBI image codec to cause memory corruption, potentially leading to code execution or crashes.

- **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:** 26 Sep 2025
- **Updated:** 26 Sep 2025
- **Also known as:** DEBIAN-CVE-2025-11015, GHSA-jmm8-jqf2-7x8j, UBUNTU-CVE-2025-11015

## What is CVE-2025-11015?

CVE-2025-11015 is a medium-severity memory corruption vulnerability in OGRECave Ogre, published on 26 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A weakness has been identified in OGRECave Ogre up to 14.4.1. Impacted is the function STBIImageCodec::encode of the file /ogre/PlugIns/STBICodec/src/OgreSTBICodec.cpp. This manipulation causes mismatched memory management routines. The attack is restricted to local execution. The exploit has been made available to the public and could be exploited.

Weakness: CWE-762 (Mismatched Memory Management Routines), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2025-11015 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11015 is a medium-severity memory corruption vulnerability in OGRECave Ogre, published on 26 Sep 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-11015 exists.

Affected product: OGRECave Ogre. 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-11015/ (Markdown: https://insights.sbomify.com/CVE-2025-11015/index.md)
```

## Sources

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

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