CVE-2025-11017VulnerabilityPublished 26 Sep 2025

CVE-2025-11017: OGRECave Ogre · NULL Pointer Dereference

Affects OGRECave OgreSource 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.2% chance of exploitation in 30 days – higher than 10% 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:N/VI:N/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: None
Vulnerable system integrity: None
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: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within 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 26 Sep 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

Affected software

Product	Affected	Fixed in
OGRECave Ogre	Affected =14.4.0 =14.4.1	Fixed in–

AI-suggested

To mitigate CVE-2025-11017, European organizations should first identify all instances of Ogre 14.4.0 and 14.4.1 within their environments, including embedded applications and development tools. Since no official patches are currently available, organizations should implement strict local access controls to limit who can execute or manipulate applications using Ogre. Employing application whitelisting and privilege restrictions can reduce the risk of local exploitation. Monitoring for abnormal application crashes or log anomalies related to Ogre's logging subsystem can provide early detection of exploitation attempts. Developers and integrators should consider recompiling Ogre with additional null pointer checks or applying community-supplied patches if available. Additionally, organizations should engage with the OGRECave project or vendor for updates and patches. In the longer term, upgrading to a fixed version once released is essential. Network segmentation to isolate systems running vulnerable software and enforcing endpoint security policies will further reduce risk. Finally, educating local users about the risks of executing untrusted code locally can help prevent exploitation.

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.

Impact

For European organizations, the impact of CVE-2025-11017 is primarily related to potential denial of service conditions in software products or services that embed the affected Ogre versions. Organizations using applications relying on Ogre 14.4.0 or 14.4.1 could experience crashes or service interruptions if an attacker with local access exploits this vulnerability. This could affect development environments, simulation software, gaming platforms, or any internal tools leveraging Ogre for rendering. However, since exploitation requires local access and no remote attack vector exists, the risk to large-scale operational disruption or data breach is limited. The vulnerability could be leveraged by malicious insiders or attackers who have already gained local foothold to cause instability or disrupt services. Given the lack of impact on confidentiality or integrity, the primary concern is availability degradation. European organizations with strict uptime requirements or those in sectors relying on real-time rendering (e.g., automotive, aerospace, or media production) may find this vulnerability more impactful. The absence of known exploits in the wild currently reduces immediate risk, but the public availability of exploit code necessitates prompt attention.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Sep 2025, 14:11 UTC

Technical details

References

Community reviews

Related threats