# CVE-2025-11017: OGRECave Ogre OgreLogManager.cpp stream null pointer dereference

> A local attacker can cause a denial of service via null pointer dereference in the Ogre 3D engine's LogManager.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/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-11017, GHSA-fj7w-qw6p-vg55, UBUNTU-CVE-2025-11017

## What is CVE-2025-11017?

CVE-2025-11017 is a medium-severity 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 vulnerability was detected in OGRECave Ogre up to 14.4.1. The impacted element is the function Ogre::LogManager::stream of the file /ogre/OgreMain/src/OgreLogManager.cpp. Performing manipulation of the argument mDefaultLog results in null pointer dereference. The attack must be initiated from a local position. The exploit is now public and may be used.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

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

It affects 1 product.


Products: Ogre3d Ogre.

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

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

## Is CVE-2025-11017 being exploited?

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

## Other vulnerabilities in OGRECave Ogre

- [CVE-2025-11014](https://insights.sbomify.com/CVE-2025-11014/): OGRECave Ogre Image OgreSTBICodec.cpp encode heap-based overflow (medium 4.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11017 is a medium-severity 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-11017 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-11017/ (Markdown: https://insights.sbomify.com/CVE-2025-11017/index.md)
```

## Sources

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

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