OSV-2026-969 Heap-use-after-free in Ogre::VertexData::convertPackedColour
Not scored
Published
Check this codebase for OSV-2026-969 and fix it if it is affected.
What it is: OSV-2026-969 is an use after free vulnerability in ogre, published on 26 Jun 2026.
Exploitation: There is no known exploitation of OSV-2026-969 in the wild and no public exploit code.
Affected packages and fixed versions:
- ogre (OSS-Fuzz): affected all versions; no fix listed
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/OSV-2026-969/ (Markdown: https://insights.sbomify.com/OSV-2026-969/index.md)
A heap-use-after-free in Ogre 3D's vertex data conversion allows attackers to cause crashes or potentially execute code via malicious mesh files.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is OSV-2026-969?
OSV-2026-969 is an use after free vulnerability in ogre, published on 26 Jun 2026.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=527766102
Crash type: Heap-use-after-free READ 1
Crash state:
Ogre::VertexData::convertPackedColour
Ogre::MeshSerializerImpl::readGeometry
Ogre::MeshSerializerImpl::readMesh
Which versions are affected by OSV-2026-969?
1 open source package ship an affected version, including ogre.
| Package | Affected | Fixed in |
|---|---|---|
ogre OSS-Fuzz | All versions | None |
How do I fix OSV-2026-969?
No fix has been published for OSV-2026-969 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is OSV-2026-969 being exploited?
There is no known exploitation of OSV-2026-969 in the wild and no public exploit code.